4 ms·
> "The language could make those guarantees if it wanted to" > "Of course by C's nature there are limits" You seem to acknowledge the fact that most of the un
by uasm 7y ago
> "The language could make those guarantees if it wanted to"
> "Of course by C's nature there are limits"
You seem to acknowledge the fact that most of the undefined behaviors in C are essentially born out of compromise. Those compromises were driven by principles such as "keep the power in the hands of developers", "don't impose unnecessary restrictions", "keep the language clean", "avoid hidden runtime magic". The end results reflect that.
As I've mentioned in my previous comment, there's no "one size fits all", so the language makes it trivial for you to roll out your very own runtime magic (à-la Zig/Nim) which suits you best. Why is that a bad thing?