← Back to context

Comment by estebank

2 days ago

The thing that has changed is that there are spaces where security is being taken more seriously, and C's memory unsafety became a deal breaker there. I do think that providing a mechanism to run existing C software that isn't performance sensitive in a way that mitigates its limitations is very worthwhile.

I think the "static analysis" and the "runtime checks" approaches are complementary, not in opposition, making any noise around having to choose one or the other moot.

One would think that by now it would also be on WG14 roadmap for language evolution.

Same in regards to WG21, while more active in improving safety, there are plenty of politics between the profiles approach faction and everyone else.