imports - 2 years later

[jcc7]

In article <dupjbv$jti$1 at digitaldaemon.com>, Ant says...
>
>In article <duphvm$hnm$1 at digitaldaemon.com>, bobef says...
>>
>>I had the same problem. Removing std.something from one of the modules 
>>where it wasn't used at all fixed the problem...
>>
>>Ant wrote:
>>> the interesting thing is that I had a
>>> private import std.c.stdio;
>>> in one module that would supply std.string to a bunch of other modules
>>> 
>
>I think this is much more important then Walter does.
>This will prevent D to be used in any sizeable project that involves
>more then one coder.
>Is somebody else adds the wrong import on some module I never saw my
>code will break :(
>
>Ant

I think it's an important issue because I know I've wasted a lot of time dealing
with similar import errors, but I don't think that Walter actually needs to
change the "rules of importing". More descriptive (i.e. helpful) error messages
might be all that is needed. 

I've posted some suggestions about this in the past, but I don't think Walter
has had a chance to work on it yet (assuming he even agrees that situation needs
to improve).

jcc7