On Thursday, 23 January 2014 at 11:43:07 UTC, Leandro Motta
Barros wrote:
Hi,
Do anyone has any feedback about his issue? I (and at least one
more user)
believe that the "package.d" feature behaves strangely (please,
see the
examples in my original post).
Thanks a lot,
You should probably file a bug. I think this change should be
valid (it sounds like it wouldn't work, but didn't test)
------
static import mypackage.util;
alias sym = mypackage.util.func;
------
Changed to:
------
import mypackage;
alias sym = mypackage.util.func;
------
That is to say, changing from a specific module import to a
"package" import should still allow fully qualified names so that
code would not be required to change.
