https://issues.dlang.org/show_bug.cgi?id=19665
--- Comment #5 from Vladimir Panteleev <dlang-bugzi...@thecybershadow.net> --- (In reply to Adam D. Ruppe from comment #4) > It does bug me that it is inconsistent with other modules though: in no > other case does the filename matter (aside from automatic lookups). You are > allowed to have blargh.d with module whatever.you.want;. So why must this > one special case require the package.d filename? Personally, I always considered that mismatching module and file names was just the implementation being overly permissive. It only works with certain build systems and breaks a number of other assumptions for various tooling, so I'm happy to write that off in the "it works but don't do that" category. --
