Nested public imports - bug or feature?

[Dicebot via Digitalmars-d]

On Thursday, 13 August 2015 at 13:42:42 UTC, Jonathan M Davis 
wrote:
> I confess that I don't particularly like that this is legal 
> (and I think that public imports tend to get a bit hinky 
> because of the fact that they create aliases), and I'm not 
> quite sure how you could use it form "import hygiene," but I 
> also don't see how this could work any other way if scoped, 
> public imports are allowed.

It won't work if you define importing as adding module to 
internal scope symbol lookup table, without actually adding 
imported symbols to scope.