serge-sans-paille wrote: > And still, I think annotating particular methods of containers is not > scalable since standart `std::vector` and friends realistically may not have > that. We can probably make an option to list all methods that are allowed to > be called on moved object (similar to > https://clang.llvm.org/extra/clang-tidy/checks/bugprone/use-after-move.html#cmdoption-arg-InvalidationFunctions) > but Its not ideal as well.
I don't understand that argument. As a developer, I'd feel pretty happy to have a high-level way to state the behavior of each class wrt. being moved from. https://github.com/llvm/llvm-project/pull/216121 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
