diff options
| author | Kinuko Yasuda <kinuko@chromium.org> | 2023-09-14 20:45:56 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-09-14 20:45:56 +0200 |
| commit | 0612c9b09a2b8609069eeca0f08957fdb5de45fa (patch) | |
| tree | 0b63199bc35a7e7c6d1ac9fa7fe9c3425b41e37f /llvm/docs/tutorial | |
| parent | f45f1c3585e6b50dd134b3b23ac14d1ca322dc6f (diff) | |
| download | llvm-0612c9b09a2b8609069eeca0f08957fdb5de45fa.zip llvm-0612c9b09a2b8609069eeca0f08957fdb5de45fa.tar.gz llvm-0612c9b09a2b8609069eeca0f08957fdb5de45fa.tar.bz2 | |
[clang][dataflow] Ignore assignment where base class's operator is used (#66364)
In C++ it seems it is legit to use base class's operator (e.g. `using
Base::operator=`) to perform copy if the base class is the common
ancestor of the source and destination object. In such a case we
shouldn't try to access fields beyond that of the base class, however
such a case seems to be very rare (typical code would implement a copy
constructor instead), and could add complexities, so in this patch we
simply bail if the method operator's parent class is different from the
type of the destination object that this framework recognizes.
Diffstat (limited to 'llvm/docs/tutorial')
0 files changed, 0 insertions, 0 deletions