[frustration, sorry] Import conflict madness.

[Dawid Ciężarkiewicz]

You write your great soft in D. You're coding with smile because everything
in seems to be so good. You added few new files, new classes. Porting your
project from C++ to D seems to be so good idea. You type "make".

And then out of nowhere: BANG!!!

battle.d(31): import battle.map conflicts with cell.cell.map at
cell/cell.d(29)

GAME OVER!

You're stuck with this nothing telling you error message. You start
wondering what is wrong. 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.

Please Walter - fix this. It is sooooooo frustrating and everyone confirms
that. It's something that all D people hits once or more.