On Thursday, 22 September 2016 at 15:02:01 UTC, Lodovico Giaretta
I think that having package.d provides a better layout. Look at
the difference between this:
Having to put part of a package outside the package folder is
ugly to see and a bit more difficult to manage.
Yes that does seem like a nice benefit. What do you think about
hierarchical modules? Do you think we should have supported
modules that also have modules underneath them? i.e.
Or do you think it's fine to require the higher level modules to
exist in package.d files?
It just seems odd because the modules aren't packages. I suppose
I would understand if hierarchical modules are discouraged, is
that the case? I ran into this problem because I'm working on a
.NET to D transpiler, and put all the symbols in a .NET namespace
into the same D module. So currently I have to do this:
but I think it would make more sense to have this: