I have a directory structure like this (names are changed, but
essentially they shouldn't matter):
source/foo/package.d
source/foo/bar/package.d
with foo.package.d containing a public import of foo.bar, and foo.bar
containing various public imports from elsewhere.
I get the following message:
Error: module foo.bar from file source/foo/bar/package.d conflicts with
package name bar
What? I have no idea why this works in other places but not here. Is
this a real thing? Has anyone experienced this and can point at a
bugzilla for it?
I found this fixed issue from 2013:
https://issues.dlang.org/show_bug.cgi?id=10302 which has similar error
message.
If I remove the module definition it starts compiling. Is that right?
I can't reproduce with a small example. Before I try and go through the
process to reduce this, just wanted to see if anyone knows about this.
-Steve
