News for hackers. Stuff that matters.
Re:Catching use-after-move C++ bugs with Clang's consumed an... by badamp on Wednesday July 10, 2019 @04:13PM (#20406033)
> I've been writing C++ for 21 years now (started when I was 14).

So? As far as I know this could be 1 year+ 20 repeats.

In contrast to your experience, I missed move semantics since the early 2000s. It’s not just to avoid copies.

How about the ability to avoid pointers, aliasing, and allocation. Move semantics afford more than just avoiding a copy.

Re:Catching use-after-move C++ bugs with Clang's consumed an... by rsp1984 on Wednesday July 10, 2019 @07:26PM (#20407636)
Please. May I ask that you provide some code examples?