On 2/9/2012 1:48 AM, Sönke Ludwig wrote:
Another thing is that while private selective imports are not public anymore,
private renamed imports now conflict in other modules in this scenario:
---
module a;
import std = b;
module b;
import a;
void f(){ std.stdio.writefln("X"); } // Error: std at conflicts with std at
a.d(2)
---
I think it should conflict - can't have std as both an alias and a package.
I'm also getting an error in cgcs.c line 354 on a "piece" of code that
previously errored on line 162/cgcs.c (the fixed bug 6177). I will run
dustmite on it and see where it comes from. Not sure if the two are related to
the same root cause or if this is a regresseion.
I need a test case.
_______________________________________________
dmd-beta mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/dmd-beta
