Thread overview | |||||
---|---|---|---|---|---|
|
June 09, 2015 [Issue 9664] Make directory in import path like "a.b.c" a properly supported feature | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=9664 Andrei Alexandrescu <andrei@erdani.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |D2 -- |
January 06, 2019 [Issue 9664] Make directory in import path like "a.b.c" a properly supported feature | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=9664 Nick Treleaven <nick@geany.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick@geany.org --- Comment #5 from Nick Treleaven <nick@geany.org> --- > there are times where you end up having a directory containing a single directory containing a single directory, ..., just because of the module path This is a valid reason, but if we want to support this I think it needs clear identifying syntax, something like `import "a.b.c".d` (although this doesn't work for fully qualifying symbols in code). Adding more module location ambiguity harms understandability (even with errors on conflicts), and this situation seems quite niche. I think it should be an error for a package directory name not to be a valid single identifier. Suggest we close as WONTFIX. -- |
December 17, 2022 [Issue 9664] Make directory in import path like "a.b.c" a properly supported feature | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=9664 Iain Buclaw <ibuclaw@gdcproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P4 -- |
Copyright © 1999-2021 by the D Language Foundation