Nested public imports - bug or feature?

[Timon Gehr via Digitalmars-d]

On 08/20/2015 01:25 AM, Walter Bright wrote:
>>
>> I want to use it as an import hygiene idiom but not entirely sure if this
>> behavior can be relied upon (or it is just a side effect of imports being
>> implemented as aliases currently).
>
> It has nothing to do with aliases.
>
> Imports work the same way as template mixins do. They share the same
> implementation code.

This is exactly the right way to do it.

Note that alias this doesn't get this right currently. It can be 
hijacked by local imports.