Shadowing of members
mist
none at none.none
Thu Jan 10 01:03:24 PST 2013
> There is a rationale for such checks, but I argue that the
> place of these checks is not in the compiler itself, but in a
> separate tool.
This. Compiler should never issue errors on code that may be
correct (at least in scope of language coding guidelines). And
warnings should just vanish from existence. Checking code for
_possible_ bug-prone idioms is job of static analysis tool, not
compiler.
More information about the Digitalmars-d
mailing list