3 ms·
> given the built-in "succeed or die" macros that simplify code at the cost of reliability Most of those are linted for, so you can use them to speed developme
by swsieber 7y ago
> given the built-in "succeed or die" macros that simplify code at the cost of reliability
Most of those are linted for, so you can use them to speed development but still be aware that they shouldn't be there in production code.
- falcolas 7y agoThese points are around language design and implementation; linting is an additional set of tools outside the scope of the language itself. Whether it should or shouldn't be in production, following Ada's rules it wouldn't be allowed in the code in the first place.
- swsieber 7y agoI'd argue that lints are part of the language - they are run as part of the compiler, and block code from compiling, like the "must use" lint. That said, they are configurable, so I see your point - they are more permissive than what Ada allows OTOH, I believe you can turn lint warnings into hard errors for only production, allow for fast development but programmatically disallowing them from reaching production. But again, thats configurable.