On 09/10/14 22:06, Dicebot wrote:
I think this is an issue with the import resolution, not module system. The way it is implemented right now DMD stops searching for object.d / object.di once it has found one. So while your module name is not interpreted as "object" _original_ object.di does not get imported and you get lot of different issues from missing declarations.
So it just picks the first filename matching "object" and doesn't care about its module name.
-- /Jacob Carlborg
