A few days ago the C++ Alliance announced a partnership with legendary Sean Baxter, author of the Circle language and compiler, to develop a proposal for a Rust-like borrow checker in C++
https://cppalliance.org/vinnie/2024/09/12/Safe-Cpp-Partnership.html
=> More informations about this toot | More toots from urixturing@hachyderm.io
A fairly advanced draft of the proposal is available, and it basically is a clone of Rust's concepts, using a new C++ borrow operator ^. I enjoyed reading it, being a C++ guy myself now working with Rust.
=> More informations about this toot | More toots from urixturing@hachyderm.io
What I enjoyed the most is a practical proposal that cuts through all the noise of the C/C++ vs Rust drama. Oh my god, Sean Baxter committed the worst sin: adding a borrow checker to C++. And he didn't even hide that it comes directly from Rust!
In a single move, it shows that programming languages should not become tribal identities, and that is fine to just steal good solutions from other languages.
=> More informations about this toot | More toots from urixturing@hachyderm.io
@urixturing This is so wonderful!
I really think that the way forward is for programming languages to copy features from each others, so users of one language don't have to stop using it just because it's missing a great feature that could have been easily integrated into it.
=> More informations about this toot | More toots from lulu@hachyderm.io
Similarly, see the Rust memory ordering model. From the Rustonomicon:
Rust blatantly just inherits the memory model for atomics from C++20
Yeah, memory models are hard. Things like AcqRel and SeqCst can induce lovecraftian madness. So just steal it, and say it so.
=> More informations about this toot | More toots from urixturing@hachyderm.io
In conclusion to this unexpected thread: programming languages are imperfect tools that (disproportionately) reflect the worries and paradigms from when they were designed.
text/gemini
This content has been proxied by September (ba2dc).