Bug 386 – anonying "import conflicts" for years!!! Please fix it ASAP!!!

Please do a search "import conflicts" on www.digitalmars.com: People have been complaining this for years: http://www.digitalmars.com/d/archives/digitalmars/D/25213.html http://www.digitalmars.com/d/archives/digitalmars/D/learn/2368.html http://www.digitalmars.com/d/archives/digitalmars/D/15503.html I wonder why this is still not fixed: 1) *private* imports should never conflict with each other!!!!!! 2) if you cannot fix 1), at least give better error message: as suggested in http://www.digitalmars.com/d/archives/digitalmars/D/15503.html Is it possible for DMD to give at least a little nicer error message, like... core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48), try importing std.math to core/frame.d

http://www.digitalmars.com/d/archives/digitalmars/D/25213.html *sigh* Is it possible for DMD to give at least a little nicer error message, like... core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48), try importing std.math to core/frame.d or core/rotozoom.d(26): import core.rotozoom.std conflicts with core.texture.std at core/texture.d(48), however due to the nature of this error message, the problem lies in neither of the given files, good luck finding it! Especially if you are not the sole developer, and have no clue which file it could possible be. just frusterating... had to rant, sorry. - clayasaurus and more: http://www.dsource.org/forums/viewtopic.php?p=2830#2830

Fixed DMD 0.169