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 threadLucas Werkmeister
@Migueldeicaza This looks interesting, and is certainly an impressive technical achievement, but I'm worried that I see no mention of the ever-increasing cost of maintaining a toolchain that can can compile all the possible feature combinations. E.g. "The compiler still knows how to perform function overloading", and it has to keep this knowledge ("perhaps the most complex part of C++"!) until the end of time.
Jan 24, 2023 at 6:07pmWeb
Show threadLucas WerkmeisterJan 24, 2023
@Migueldeicaza I'm also not convinced all desirable features work as per-file flags, e.g. it's not clear to me how a per-file borrow checker would interact with other source files that don't specify whether they own, borrow or mutably borrow something...