[frustration, sorry] Import conflict madness.

[Sean Kelly]

Derek Parnell wrote:
> 
> I have yet to find a *need* for public imports.

I have.  Implementing C headers it's common for an alias to be declared 
in one header that must be visible in other headers.  Sure, you could 
require the user to manually import both headers, but that's 
non-intuitive and a tad annoying.  And the alternative (private import 
combined with aliasing symbols to expose them piecemeal) results in 
symbol collision problems.


Sean