diff options
| author | Martin Boehme <mboehme@google.com> | 2021-03-05 13:16:00 +0100 |
|---|---|---|
| committer | Martin Boehme <mboehme@google.com> | 2021-03-05 15:05:09 +0100 |
| commit | e67d91faec2183789b220c15444929fb2efa6ecd (patch) | |
| tree | 8e9358966fee60cdbd83aeca447b5375ca9f7ee1 /llvm/lib/Bitcode/Reader/BitcodeAnalyzer.cpp | |
| parent | 5b3fc7180c8e4a2c57946d5e3cc325744a770717 (diff) | |
| download | llvm-e67d91faec2183789b220c15444929fb2efa6ecd.zip llvm-e67d91faec2183789b220c15444929fb2efa6ecd.tar.gz llvm-e67d91faec2183789b220c15444929fb2efa6ecd.tar.bz2 | |
[clang-tidy] Use-after-move: Ignore moves inside a try_emplace.
We have no way to reason about the bool returned by try_emplace, so we
simply ignore any std::move()s that happen in a try_emplace argument.
A lot of the time in this situation, the code will be checking the
bool and doing something else if it turns out the value wasn't moved
into the map, and this has been causing false positives so far.
I don't currently have any intentions of handling "maybe move" functions
more generally.
Reviewed By: sammccall
Differential Revision: https://reviews.llvm.org/D98034
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeAnalyzer.cpp')
0 files changed, 0 insertions, 0 deletions