kelbon wrote: > A few thoughts: > > 1. How does this work with conditional control flow? > 2. `[[clang::drop]]` feels like a bad name. I have absolutely no idea without > looking it up what it drops. > 3. Why doesn't static analysis catch this already? There is e.g. > `bugprone-use-after-move`, which should probably catch this.
forbidding usage not always linked with std::move. About conditional control flow, implementation not yet 100% complete, but it should behave like forbidding if in any branch variable may be dropped https://github.com/llvm/llvm-project/pull/204318 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
