Thread overview | ||||||||
---|---|---|---|---|---|---|---|---|
|
June 19, 2014 [Issue 12659] Named mixin templates conflict | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=12659 Vlad Levenfeld <vlevenfeld@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vlevenfeld@gmail.com -- |
September 17, 2016 [Issue 12659] Module level mixin templates conflict | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=12659 Marco Leise <Marco.Leise@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Marco.Leise@gmx.de Summary|Named mixin templates |Module level mixin |conflict |templates conflict --- Comment #1 from Marco Leise <Marco.Leise@gmx.de> --- Generally, symbols mixed in at module level conflict. E.g.: mixin template Preparer() { bool isPrepared; } when mixed into multiple modules causes conflicts when accessing `isPrepared`. In particular `fully.qualified.module.name.isPrepared` does not help the compiler distinguish the symbols either. -- |
December 17, 2022 [Issue 12659] Module level mixin templates conflict | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=12659 Iain Buclaw <ibuclaw@gdcproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P3 -- |
December 13 [Issue 12659] Module level mixin templates conflict | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=12659 --- Comment #2 from dlangBugzillaToGithub <robert.schadek@posteo.de> --- THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/dmd/issues/18821 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB -- |
Copyright © 1999-2021 by the D Language Foundation