News for hackers. Stuff that matters.
Re:Catching use-after-move C++ bugs with Clang's consumed an... by rsp1984 on Wednesday July 10, 2019 @07:22PM (#20407616)
I appreciate your reply. But frankly, why would someone "accidentally" copy something by value?

I don't mean to sound arrogant but if someone is writing C++ at a level where he/she does accidental copies then that's a very clear sign to me to stay the hell away from move semantics and other advanced features.

I personally find things being copied by default a nice feature. It's more consistent than "PODs by value, objects by reference" such as in Java.

Re:Catching use-after-move C++ bugs with Clang's consumed an... by steveklabnik on Wednesday July 10, 2019 @07:58PM (#20407837)
> But frankly, why would someone "accidentally" copy something by value?

Well; https://groups.google.com/a/chromium.org/forum/#!msg/chromiu...

Re:Catching use-after-move C++ bugs with Clang's consumed an... by damnyou on Thursday July 11, 2019 @12:23AM (#20409111)
There is no such thing as a bad programmer, only bad tooling. C++ is bad tooling.
Re:Catching use-after-move C++ bugs with Clang's consumed an... by patrick5415 on Thursday July 11, 2019 @03:20AM (#20409702)
A craftsman doesn’t blame his tools.
Re:Catching use-after-move C++ bugs with Clang's consumed an... by damnyou on Thursday July 11, 2019 @04:03PM (#20415237)
A great craft recognizes how important good tools are.
Re:Catching use-after-move C++ bugs with Clang's consumed an... by cozzyd on Thursday July 11, 2019 @01:33AM (#20409359)
The horrors I've seen in academic code speak otherwise.