News for hackers. Stuff that matters.
Re:Moving to a provenance-aware memory object model for C: p... by vvanders on Sunday April 14, 2019 @12:24PM (#19660277)
C++ makes it really easy to corrupt the heap or stack which depending on tooling can take days or weeks to track down. I don't mind trading a bit of flexibility with and optional escape hatch (unsafe).

I'm really skeptical of backporting Rust's wins to C++. The concept of mutability cuts across the language and I don't see how you do it without bifrucating an already complicated language.

Re:Moving to a provenance-aware memory object model for C: p... by UncleEntity on Sunday April 14, 2019 @01:12PM (#19660481)
> The concept of mutability cuts across the language and I don't see how you do it without bifrucating an already complicated language.

How hard would it really be for someone to write a static analyzer for C++ that ensures there is only one non-const reference/pointer to an object active at any given time?

Throw in an object lifetime tracker for allocs and you'd have pretty safe C++ without having to rewrite a billion line of code.

Re:Moving to a provenance-aware memory object model for C: p... by pjmlp on Sunday April 14, 2019 @01:23PM (#19660541)
Microsoft and Google are having a go at it.