Miguel de Icaza ᯅ🍉Jan 24, 2023

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
Show threadDavid MooneyJan 24, 2023
@Migueldeicaza More than a whiff of "I do not know what the language of the year 2030 will look like but it will be called C++" to this.
Show threadAdam RoachJan 24, 2023
@davidm @Migueldeicaza Having read a little bit more of the essay now, David's comment hits the nail on the head for me. The syntax of these new features is alien to a lifelong C++ programmer, and learning to make a borrow checker happy is the same experience regardless of the underlying language. If you're going to learn a safe language, why would it be the C++ of tomorrow rather than the Rust of today?
Show threadRoy Triesscheijn
@abr @davidm @Migueldeicaza I believe the whole point here is too move to something more modern when you have large C++ code base that you want to continue to work on seemlessly. For a standalone project that doesn't have to integrate with C++ there are a lot of good options.
Dec 25, 2023 at 9:25amTusky
Show threadRoy TriesscheijnDec 25, 2023
@abr @davidm @Migueldeicaza oh wait this whole discussion is a year old.... Oops not sure how I got here 😁
Show threadAdam RoachDec 25, 2023
@roytries @davidm @Migueldeicaza you and everyone else. There’s been quite a few interactions with this post today and yesterday for some reason.