DMD 2.071.1 and Issue 15925 - [REG 2.071] Import declaration from mixin templates are ignored

[qznc via Digitalmars-d]

On Thursday, 30 June 2016 at 08:08:13 UTC, Mathias Lang wrote:
> Author here. I originally thought the issue was that an 
> 'imported' scope
> imports are not considered anymore.
> As Walter explained in this issue and in
> https://issues.dlang.org/show_bug.cgi?id=15966 this behaviour 
> changed to
> prevent hijacking and is intended.
> So the only issue left with 15925 was that 
> `-transition=checkimport` did
> not warn about it, which Martin fixed. But since the issue was 
> not renamed
> / repurposed, it led to a confusing changelog.

I don't see this properly documented [0].

It seems that imports in mixins are not visible even if declared 
public? This means mixin imports are special?

The issue also features a "protected imported". I guess nobody 
knows what that is supposed to mean?

[0] https://dlang.org/spec/module.html#ImportDeclaration