debugging mixins

Manu via Digitalmars-d digitalmars-d at puremagic.com
Sat Oct 1 20:36:31 PDT 2016


This comes up a lot.
As far as I know, it's not solved. What shall we do?

I feel like a simple solution would be to have the compiler emit a
<filename>_mixin.d file populated with all the mixin expansions beside
the .obj files, and have the debuginfo refer to that fabricated source
file?

It might look a little bit weird jumping into code where the
surrounding scope is not visible (unless that were copied over too?),
but it's better than what we have now.

Are there any other commonly proposed solutions?


More information about the Digitalmars-d mailing list