Re:Catching use-after-move C++ bugs with Clang's consumed an...
by bsder on Wednesday July 10, 2019 @06:20PM
(#20407202)
> I'm just saying the net benefit just does not exist for stable software like librsvg or bzip2.
Are you sure?
Both of those libraries are, in fact, poster children to be rewritten in Rust as they have to eat untrusted input.
If I offered $20 on "I can find a use-after-free or undefined behavior bug somewhere in those libraries" I'm pretty sure nobody would take that bet.
Re:Catching use-after-move C++ bugs with Clang's consumed an...
by pjmlp on Wednesday July 10, 2019 @05:42PM
(#20406900)
To be faire, that is not everywhere.
The design team always has nice conversations with me, in spite of my schizophrenic view of C++ vs Rust (like both languages, see some negative issues in both), and there are places with joint community events between C++ and Rust.
> Is there something intrinsic to Rust that would lead them to this error? (no, I think not).
There is nothing intrinsic to Rust that creates this kind of problem, besides it being a different language than the project was originally written in. I'm sure Go, Swift, Haskell, Java, or any other language (with the possible exception of C++) would have similar issues. No other language community is quite as arrogant as the Rust community though.