News for hackers. Stuff that matters.
Re:Catching use-after-move C++ bugs with Clang's consumed an... by pcwalton on Thursday July 11, 2019 @12:36AM (#20409165)
> Java doesn’t have unsafe code at all, not even in standard library, and it’s very hard to interop with.

Look at Android system libraries. They use JNI all over the place.

Re:Catching use-after-move C++ bugs with Clang's consumed an... by pjmlp on Thursday July 11, 2019 @01:53AM (#20409438)
You mean like using unsafe all over the place in many third party Rust libraries?

Also Android is a poster child that Google hiring practices don't lead to the best quality of code implementation.

Re:Catching use-after-move C++ bugs with Clang's consumed an... by pcwalton on Thursday July 11, 2019 @02:19AM (#20409511)
> You mean like using unsafe all over the place in many third party Rust libraries?

Yes?

I don't think Rust is particularly more, or less, memory safe in practice than Java. They're both memory-safe languages.

Re:Catching use-after-move C++ bugs with Clang's consumed an... by pjmlp on Thursday July 11, 2019 @02:39AM (#20409571)
Ah sorry, I misunderstood your remark then.