On 18.04.2016 00:08, Bauss wrote:
On Sunday, 17 April 2016 at 21:59:38 UTC, Timon Gehr wrote:
On 17.04.2016 23:49, Bauss wrote:
On Sunday, 17 April 2016 at 21:23:58 UTC, Timon Gehr wrote:
mixin(generate());
pragma(msg,generate());
That's not a solution to the problem, because you will be
On Sunday, 17 April 2016 at 23:10:38 UTC, Adam D. Ruppe wrote:
On Sunday, 17 April 2016 at 22:08:55 UTC, Bauss wrote:
Like I also said this does not apply to normal mixins but
usually very big mixins composited of multiple mixins and
template mixins.
Why are your mixins so huge?
But yeah, I
On Sunday, 17 April 2016 at 22:08:55 UTC, Bauss wrote:
On Sunday, 17 April 2016 at 21:59:38 UTC, Timon Gehr wrote:
On 17.04.2016 23:49, Bauss wrote:
On Sunday, 17 April 2016 at 21:23:58 UTC, Timon Gehr wrote:
mixin(generate());
pragma(msg,generate());
That's not a solution to the problem,
On Sunday, 17 April 2016 at 22:08:55 UTC, Bauss wrote:
Like I also said this does not apply to normal mixins but
usually very big mixins composited of multiple mixins and
template mixins.
Why are your mixins so huge?
But yeah, I would like to see it print the error line and a few
On Sunday, 17 April 2016 at 21:59:38 UTC, Timon Gehr wrote:
On 17.04.2016 23:49, Bauss wrote:
On Sunday, 17 April 2016 at 21:23:58 UTC, Timon Gehr wrote:
mixin(generate());
pragma(msg,generate());
That's not a solution to the problem, because you will be
printing ALL
mixins and not just
On 17.04.2016 23:49, Bauss wrote:
On Sunday, 17 April 2016 at 21:23:58 UTC, Timon Gehr wrote:
mixin(generate());
pragma(msg,generate());
That's not a solution to the problem, because you will be printing ALL
mixins and not just the ones causing compilation errors.
Obviously you'll insert
On Sunday, 17 April 2016 at 21:23:58 UTC, Timon Gehr wrote:
mixin(generate());
pragma(msg,generate());
That's not a solution to the problem, because you will be
printing ALL mixins and not just the ones causing compilation
errors.
On 17.04.2016 23:18, Bauss wrote:
Can there please be implemented something to retrieve the generated
mixins that causes compiler errors; like perhaps a flag you pass that
will print all mixins with compiler errors?
Sometimes when you create highly dynamic mixins it can be hard to
identify
Can there please be implemented something to retrieve the
generated mixins that causes compiler errors; like perhaps a flag
you pass that will print all mixins with compiler errors?
Sometimes when you create highly dynamic mixins it can be hard to
identify errors in them, because you might
