DIP10005: Dependency-Carrying Declarations is now available for community feedback

[Walter Bright via Digitalmars-d]

On 12/16/2016 11:59 AM, Andrei Alexandrescu wrote:
> Soon the naive approach "let's replace this import with a static import and
> rebuild" ran into the midst of a comedy of errors. Code in various other modules
> fails to compile. Sometimes (happy case) the error indicates the symbol that is
> not seen, which is easy to fix. Other times (as you may see if you try to touch
> the PR above) there is zero indication on where the problem originates.

The switch:

     -verrors=spec

is very useful here. It prints the errors otherwise gagged when inside 
__traits(compiles,...).