Opportunity

[Timothee Cour]

> I know it is hard to balance these type of errors, but unused imports and
> variables seems a bit extreme.

seems like go won't support temporarily suppressing such errors (see
http://weekly.golang.org/doc/faq#unused_variables_and_imports) (nor in
fact having compile flags affecting semantics, so no
version(identifier) constructs).

However D should have opt-in flags for those:
--warn_unused_variable
--warn_unused_import
--warn_unused_lib (for pragma lib statements)
--warn_unused_version (for unused version identifiers, indicating a
potentially mis-spelt version identifier given at compile time)
--warn_unreachable_code
likewise, with error instead of warn

Is there any work on that?