https://issues.dlang.org/show_bug.cgi?id=18517
Iain Buclaw changed:
What|Removed |Added
Priority|P1 |P3
--
https://issues.dlang.org/show_bug.cgi?id=18517
--- Comment #5 from Steven Schveighoffer ---
I wasn't a part of that conversation, but the "feature" makes no sense -- if
you want to import a module and it doesn't reside at the filename that you
import, then the system can't find that module. It
https://issues.dlang.org/show_bug.cgi?id=18517
--- Comment #4 from Jonathan Marler ---
> I would expect that if a module is loaded via using the filesystem, and the
> module name doesn't match how it was found, then this should be an error.
> Anything else seems to strain your sanity!
I
https://issues.dlang.org/show_bug.cgi?id=18517
--- Comment #3 from Steven Schveighoffer ---
Hm... I didn't realize that the module identifier was not identical to the
filename. That is interesting. It's not clearly stated in this bug report that
this is a requirement to get the error to occur --
https://issues.dlang.org/show_bug.cgi?id=18517
--- Comment #2 from Walter Bright ---
Jonathan Marler's Relevant Pull Requests:
Fix module/import order invariance:
https://github.com/dlang/dmd/pull/7900
Interpret imports the same regardless of other modules passed on the command
line:
https://issues.dlang.org/show_bug.cgi?id=18517
Walter Bright changed:
What|Removed |Added
CC||bugzi...@digitalmars.com
See
https://issues.dlang.org/show_bug.cgi?id=18517
Steven Schveighoffer changed:
What|Removed |Added
CC||schvei...@yahoo.com
https://issues.dlang.org/show_bug.cgi?id=18517
--- Comment #1 from Jonathan Marler ---
Added 2 tests to dmd for this bug here: https://github.com/dlang/dmd/pull/8165
but the PR was rejected. Razvan doesn't think tests should be pushed to dmd by
themselves (without their