Debuggers for D

[Michael Coupland]

In an ideal world there would also be a full "stack trace" of 
information where the mixin was used... The more complex metaprogramming 
becomes, the more important it is to be able to (easily!) debug the 
compilation process itself.

I don't pay too close attention to the D community, and clearly runtime 
debugging support is a higher priority, but is 
mixin/template/metaprogramming debugging on anyone's radar at all? It's 
nice to have powerful metaprogramming support in D, but if the only way 
to debug a wacky template is via compiler error messages, it's just as 
bad as having to debug a normal program only using crash stack traces.

Jascha Wetzel wrote:
> it wouldn't make any sense to assign any line other than the one of the
> mixin statement. hence this isn't much of a problem.
> 
> DMD for windows assigns the line following the mixin statement to the
> code. well, kind of... it looks a bit like the current behaviour is not
> intended.
> 
> Ary Manzana wrote:
>> John Demme wrote:
>>> I'm pretty sure that a fair of the
>>> linenumber and file information is wrong
>> Imagine when mixins will come into play. What line and number
>> information can be recorded for symbols generated at compile time? :-O