Alexander Bothe
Alexander Bothe
This is not gonna be implemented soon, as ctfe obviously requires all D code elements to be interpreted in a pseudo-runtime - and this is something which I haven't even...
Nah, not providing complete sets for completion..that's way too hardcoded. The only thing I'd support would be to let a third tool precompile all mixins and return them via stdout,...
How is this possible? Ahh, no, this would require to analyse COFF/OMF files - and at this point, I'm leaving the fields :D .. It's enough to handle these things...
Ah, no, that was too complex to handle atm. I just need the mixed-in strings. From there on I could evaluate everything else on my own.
no no, I don't need any definitions, just the string that is being created. So I'd prefer a simple file that gives me some file/line/column Generated string lookup - this...
 Caution: Only functions with a single return statement will work! :P
It's somehow not working with `string inty(alias a)()`, but this is not a primarly ctfe-related issue anymore.
mono-d 1.38? tbh I haven't seen anything like the bar declaration before. But yes, besides x and y, w should be shown.
w is shown in v1.4.14 I won't do the z case for now.
1) Hmm. 2) IIRC I already had a discussion with somebody about these flags and how they're used..