Skip Navigation

The empire of C++ strikes back with Safe C++ proposal

www.theregister.com The empire of C++ strikes back with Safe C++ proposal

You pipsqueaks want memory safety? We'll show you memory safety! We'll borrow that borrow checker

The empire of C++ strikes back with Safe C++ proposal
55

You're viewing a single thread.

55 comments
  • The big downside is that, for backwards compatibility, the default must still be unsafe code. Ideally this could be toggled with a compiler flag, rather than having to wrap most code in "safe" blocks (like rust, but backwards).

    One potential upside that people don't seem to be discussing is that the safe subset could also be the place to finally start cutting down the bloat of C++. We could encourage most developers to write exclusively in the safe subset, and aim to make that the "much smaller and cleaner language" trying to get out of C++.

You've viewed 55 comments.