Skip to content

Change reference of misc-use-after-move to bugprone-use-after-move #496

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
axgillies merged 2 commits into from
Jun 26, 2025
Merged

Change reference of misc-use-after-move to bugprone-use-after-move #496

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e578539
Change reference of misc-use-after-move to bugprone-use-after-move
proteusvacuum Nov 8, 2024
93b8774
Merge branch 'master' into patch-2
axgillies Jun 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _posts/2017-10-20-totw-77.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ them, or let them go out of scope, but don’t make any other assumptions about
their state.

Clang-tidy provides some some static-checking to catch use-after move with the
[misc-use-after-move](http://clang.llvm.org/extra/clang-tidy/checks/misc-use-after-move.html)
[bugprone-use-after-move](https://clang.llvm.org/extra/clang-tidy/checks/bugprone/use-after-move.html)
check. However, static-analysis won't ever be able to catch all of these - be on
the lookout. Call these out in code review, and avoid them in your own code.
Stay away from the zombies.
Expand Down