Recent searches
Search options
Pending approval, it seems like the 0.1 milestone for Carbon will now include a detailed safety plan:
https://github.com/carbon-language/carbon-lang/pull/4880
I always felt like Carbon suffered a bit from being introduced during a memory safety inflection point, and in particular by considering safety as something that could be added later.
Lots of people have attempted this with good intentions, but I am not aware of a language conceptually situated near C++ that has successfully been able to add safety after the fact (setting aside adding some form of GC like Fil-C). This change in priorities gives Carbon a chance to avoid this trap.
@zwarich It’s a very welcome shift to see! It’s also just a really hard set of problems, unless it’s reduced to (high-value! but) limited stuff like bounds checking. Standard C++ idioms like iterators are patterned off of interior pointers into someone else’s data structure and inherit the full set of safety problems of that concept