On Sunday, 27 January 2013 at 15:24:23 UTC, Jacob Carlborg wrote:
On 2013-01-27 13:35, alex wrote:
Well, not displaying the entire module but only displaying
resolved expressions. Dunno how to do this in a proper way -
only
via tooltips or also in an extra panel? Which would be the most
useful?
If it cannot show the entire module then I think a tooltip
would be best suited.
Btw, since I'm not that involved in D's magic I definitely
haven't planned such extensive pre-compilation :D
It can be extremely helpful to see how a template/string mixin
is expanded when debugging.
It can also be fun to see how the compiler behaves internally,
i.e. scope-statements are lowered to try/catch/finally.
Any D IDE has quite a lot of expectations to live up since it
most certainly will be compared with Descent.
K..Created an extra panel, and the actual mixin evaluation is
working, too. But now there are some last adjustments required to
have the entire mechanism as few annoying and
performance-reducing as possible.
