imports - 2 years later

[bobef]

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:
> Walter, we still have:
> 
> gtk/TextBuffer.d(88): import gtk.TextBuffer.std conflicts with 
> gtk.TextChildAnchor.std at gtk/TextChildAnchor.d(46)
> gtk/TextBuffer.d(88): import gtk.TextBuffer.std conflicts with 
> gtk.TextChildAnchor.std at gtk/TextChildAnchor.d(46)
> gtk/TextBuffer.d(88): import gtk.TextBuffer.std conflicts with 
> gtk.TextChildAnchor.std at gtk/TextChildAnchor.d(46)
> gtk/TextBuffer.d(88): import gtk.TextBuffer.std conflicts with 
> gtk.TextChildAnchor.std at gtk/TextChildAnchor.d(46)
> gtk/TextBuffer.d(88): import gtk.TextBuffer.std conflicts with 
> gtk.TextChildAnchor.std at gtk/TextChildAnchor.d(46)
> gtk/TextBuffer.d(88): import gtk.TextBuffer.std conflicts with 
> gtk.TextChildAnchor.std at gtk/TextChildAnchor.d(46)
> 
> 
> these are both private import std.string;
> 
> 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
> 
> well, I know you cannot do anything about this
> and I know I cannot reduce this problem... but it's better than 2 year 
> ago! :)
> 
> Ant