2 ms·
> But he is right that "no hidden control flow" is an anti-feature. Hmmm, "no hidden control flow" is at least what I want writing distributed systems, storage
by _vvhw 5y ago
> But he is right that "no hidden control flow" is an anti-feature.
Hmmm, "no hidden control flow" is at least what I want writing distributed systems, storage engines or device drivers.
Calling it an "anti-feature" is dismissing important domains for system languages where control flow in the control plane needs to be explicitly visible, and where the necessity for things like static allocation and NASA's "The Power of 10: Rules for Developing Safety-Critical Code" mean that destructors during the lifetime of a system are an anti-pattern anyway.
- ncmncm 5y agoDestructors are a powerful tool to ensure that required events occur, an important part of safety-critical coding. Static allocation is a valuable method that is wholly compatible with use of destructors. If you imagine that freeing dynamically-allocated memory is the main use for destructors, you have utterly failed to understand them.
- _vvhw 5y agoIf I "have utterly failed to understand" destructors then I'll wear it gladly. :) I suppose we differ mostly not in our view of destructors, but in our approach to reducing dimensionality and how best to do that.