On Friday, 4 November 2022 at 16:56:59 UTC, Hipreme wrote:
[snip]
You can use any name instead. The only difference between an
ordinary source file and a package.d is the module name. For
instance, if you're inside the filesystem directory, you can
change the name to literally anything and import instead. To
make my engine's names unique I have been using a convention
for the package.d names as an abbreviation of the directory
name plus `definitions` or something like that.
If you don't plan to use private(package_name), then I don't know
what the point of it is.
