Two another more nitpicky comments: 1) Deprecation process proposal right now says this:
- remove -scope, issue warning when errors are detected - replace warnings with deprecation messages PLEASE FOR THE SAKE OF ALL DEAR NEVER EVER DO THIS Deprecations must always come first. Warnings may or may not follow later but any deprecation process must mandatory start with deprecation message, not exceptions and no excuses. 2) Ignoring `scope` for variables with no indirections. The fact that DMD is extremely accepting when it comes to nonsense declarations/attributes has been is notable contribution to harming learning curve. It often tricks new developers into thinking that their code is checked for something when in fact compiler simply silently skips extra annotations. Instead, nonsense application of `scope` to data with no indirections should be deprecated completely as part of overall deprecation process for implementing the proposal.
signature.asc
Description: OpenPGP digital signature
