From e57853999567a840cb1def68fcb603a112b59c5c Mon Sep 17 00:00:00 2001 From: Farid Rener Date: Fri, 8 Nov 2024 17:51:17 -0500 Subject: [PATCH] Change reference of misc-use-after-move to bugprone-use-after-move --- _posts/2017-10-20-totw-77.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2017-10-20-totw-77.md b/_posts/2017-10-20-totw-77.md index bb945dc6..f94b8855 100644 --- a/_posts/2017-10-20-totw-77.md +++ b/_posts/2017-10-20-totw-77.md @@ -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.