Sean Baxter not only wrote his own C++ compiler, but he authored this magnificent vision paper for the future of C++ that it moved me to reconsider my views on the safety of the language and its use future projects.

Seldom a man of my age and opinions can change his mind over something so fundamental.

Enjoy: https://github.com/seanbaxter/circle/blob/master/new-circle/README.md

circle/new-circle/README.md at master · seanbaxter/circle

The compiler is available for download. Get it! Contribute to seanbaxter/circle development by creating an account on GitHub.

GitHub
@Migueldeicaza oh boy. I recall how much you were against C++ back during our Linux/KDE/Gnome days 😅.
@glaurent some 25 years later the best interop across languages remains the limited C ABI.
@Migueldeicaza I guess so. But IMHO interop wasn't that important in retrospect.

@glaurent @Migueldeicaza Idk, it kinda boils down whether this (or similar projects) will be successful or not. GTK can quite nicely embrace the current Rust revolution and also integrates surprisingly well with C#, Qt seems to kind of struggling with C++ becoming more of a clutch than GObject was. It's impossible to migrate Qt away from C++ and crazy hard to use it from say Rust.

Their relevance is tied to the progress of C++, while GTK isn't tied to C. The same story may repeat itself in a few decades perhaps, when GTK may be bound to Rust :-p

That being said, Rust tries to be a living language that doesn't need to be replaced by the same virtue and for the same reasons outlined in the document. Most Rustaceans probably philosophically agree with the document, but don't believe that C++ or its committee is ready for such an evolutionary approach.