|
|
|
|
|
|
by awesome_dude
485 days ago
|
|
|
> Luckily there’s an easy away forward, which is to skip the step where we try to get consensus. This is true, the Benovolant Dictator model, versus the Rule by committee model problesm. Committees are notorius for having problems coming to a consensus, because everyone wants to pull in a different direction, often at odds with everyone else. Benevolent dictators get things done, but it's not necessarily what people want. And, we live in hope that they stay benevolent. |
|
|
Ultimately it may be necessary to convince standards committees, but it seems like adding features and flags into mainline clang/llvm (and/or gcc, visual studio, ...) paves the road toward improved memory safety for C at large.
For example, if clang supported it out of the box, I could imagine OpenBSD (or macOS or other OSes that use clang) eventually compiling all (or nearly all) of its C code, including kernel, library, and userland code, in safe mode - and maybe even making it the default. In fact we already see certain safety flags and compiler/runtime features being adopted.