On Saturday, 7 January 2017 at 12:29:34 UTC, ketmar wrote:
On Saturday, 7 January 2017 at 12:11:20 UTC, crimaniak wrote:
Is this a bug or documentation problem?
well, it's hard to say. package.d is one of the cases where you
*have* to provide explicit module definition. ;-) 'cause
implicit one creates module with name `package`, which is teh
keyword. and then all the hell broke loose. this actually may
be both bug and documentation problem.
Yes, removing 'module' statement leads to error on
__traits(allMembers, mixin(__MODULE__)) expression: Error:
expression expected, not 'package'.
But it's not related, I provide module statement in package.d.
