Bug 18123 – non-package module accepted for package structure

In the following forum post this issue has come up: http://forum.dlang.org/post/[email protected] file / module tree: . ├── foo │ └── bar.d └── foo.d You have a foo package, but instead of having foo/package.d the user added a foo.d file. Because the D frontend didn't detect this issue, the user was confused. I believe that when a package is present, that package should not be implementable as a non-package module (foo.d). In this case, the compiler should detect that foo.d is present and complain that foo/package.d should be used instead.

*** This issue has been marked as a duplicate of issue 17699 ***