Nested public imports - bug or feature?

[Timon Gehr via Digitalmars-d]

On 08/13/2015 05:34 PM, Dicebot wrote:
>
>> In any case, I guess we agree that this idiom should work for public
>> imports, but not for non-public ones (so the current behaviour with
>> non-public imports is accepts-invalid, but Dicebot's code should be
>> fine)?
>
> I am very curious to learn "official" answer :)

If there is only one sane/consistent/turtles/etc choice for the 
behaviour of some feature, typically, assuming that /eventually/ this 
choice will be made works.