On Friday, 21 December 2012 at 13:19:32 UTC, Peter Alexander
wrote:
On Friday, 21 December 2012 at 08:58:03 UTC, bearophile wrote:
Walter Bright:
another large source of irritation if unused imports are
errors.
In Go even unused variables are *errors* :-)
This is a tricky one. On one hand, it *is* a useful way to
catch errors, but on the other it's a constant source of
irritation when you are tinkering with code during
development/debugging.
I would consider those not as (language, compile-time) errors but
(not-)compliance with strictness-levels.
However, it is reasonable to include something like strictness
levels as part of the compiler? (think gcc with MISRA-C
integrated).
