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.
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.