https://issues.dlang.org/show_bug.cgi?id=16287
--- Comment #2 from det <2k...@gmx.net> --- https://issues.dlang.org/show_bug.cgi?id=16004 is certainly related therefore i added a 'see also' link. however i don't think it is fully sufficient WRT mixin templates. spec changes that especially effect mixin templates and are at odds with the current explanation of how mixin templates work require a fix in the documentation of mixin templates as well. remember, whole module imports through mixin templates used to work and the specs rather indicate that it should. for any problem encountered with mixin templates ppl will refer to the mixin template specs first, because it is understood that mixin templates do something extraordinary, represent a special case. also, to fix old code / write intelligent new code one needs to know that there is (now) only a (new) limitation with respect to whole module imports, not selective imports. the new import rules require 3 distinct fixes / clarifications in the specs: 1) better coverage of protection attributes 2) (enforcement of) (scoped) import rules and lookup sequence in general 3) special case: mixin templates which IS different from (2) as i understand it, https://issues.dlang.org/show_bug.cgi?id=16004 aims at (1) and (2) only. --
