On 2/5/20 6:50 PM, Steven Schveighoffer wrote:
HOWEVER, I will file a bug on this. If you have two packages claiming to
be the same module package, it would be helpful if it showed the
previously declared filename/location.
https://issues.dlang.org/show_bug.cgi?id=20563
-Steve
On 2/3/20 2:18 PM, Boris Carvajal wrote:
On Monday, 3 February 2020 at 16:35:06 UTC, Steven Schveighoffer wrote:
I can't reproduce with a small example. Before I try and go through
the process to reduce this, just wanted to see if anyone knows about
this.
I've made a few changes to the
On Monday, 3 February 2020 at 16:35:06 UTC, Steven Schveighoffer
wrote:
I can't reproduce with a small example. Before I try and go
through the process to reduce this, just wanted to see if
anyone knows about this.
-Steve
I've made a few changes to the package.d import code, one is
I have a directory structure like this (names are changed, but
essentially they shouldn't matter):
source/foo/package.d
source/foo/bar/package.d
with foo.package.d containing a public import of foo.bar, and foo.bar
containing various public imports from elsewhere.
I get the following
