[frustration, sorry] Import conflict madness.

[Derek Parnell]

On Sun, 18 Jun 2006 03:49:44 +1000, Deewiant  
<deewiant.doesnotlike.spam at gmail.com> wrote:

> Dawid Ciężarkiewicz wrote:
>> Imports probably, but ... why? It takes 15 minutes of frustrating  
>> checking
>> your files. You seek help on #D irc channel (nice people BTW) - but  
>> they can
>> not help you. They can only tell "It might be that in some unrelated  
>> file you
>> are trying to use map without importing map but are importing files  
>> that do
>> import map" which is great help but still will require you to spend  
>> great
>> amount of time finding this place.
>>
>
> Seems to me that using "private import" instead of "public import" (the  
> default)
> might help in locating this. When using "private import A;" in a module  
> B, any
> other module that imports B does not automatically import A.
>
> I have long felt that private should be the default.

I have yet to find a *need* for public imports.

-- 
Derek Parnell
Melbourne, Australia