[Issue 16287] update mixin template specs to reflect new import rules (as of 2.071)

Jul 18, 2016

det

Jul 18, 2016

Mathias Lang

Jul 19, 2016

Jul 19, 2016

Jul 05, 2017

Dec 17, 2022

Dec 15

dlangBugzillaToGithub

https://issues.dlang.org/show_bug.cgi?id=16287 Mathias Lang <mathias.lang@sociomantic.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mathias.lang@sociomantic.co | |m --- Comment #1 from Mathias Lang <mathias.lang@sociomantic.com> --- This is probably part of https://issues.dlang.org/show_bug.cgi?id=16004 (if you believe so, please mark as duplicate). I am not sure we should document the selective import behavior. To me it always seemed more of a caused by lowering rather than intended behavior (and it's the last inconsistency with the import system). --

https://issues.dlang.org/show_bug.cgi?id=16287 det <2krnk@gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://issues.dlang.org/sh | |ow_bug.cgi?id=16004 --

July 19, 2016

[Issue 16287] update mixin template specs to reflect new import rules (as of 2.071)

Posted by det

Permalink

det

Permalink

https://issues.dlang.org/show_bug.cgi?id=16287

--- Comment #2 from det <2krnk@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.

--

https://issues.dlang.org/show_bug.cgi?id=16287 Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |spec --

https://issues.dlang.org/show_bug.cgi?id=16287 Iain Buclaw <ibuclaw@gdcproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P3 --

https://issues.dlang.org/show_bug.cgi?id=16287 --- Comment #3 from dlangBugzillaToGithub <robert.schadek@posteo.de> --- THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/dlang.org/issues/4060 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB --

Forums