Orvid King
Orvid King
The feature I'm suggesting isn't intended for editing code that defines a range; rather, it's for code that uses ranges either as input or output to the function.
Yep, that would be perfect.
To reduce the amount of hard-coding required, it should be possible to extract the information you need by parsing [std.range.dummyRanges](https://github.com/D-Programming-Language/phobos/blob/master/std/range.d#L308) and instantiating it for the particular uses.
While I do see the usefulness of this, there would definitely need to be way to disable it for those of us who use the completion exploratively at times.
Any chance of a test-case?
Then we create the .sln, close it, and open the .json. Either that, or we create the .sln, and just never write it to disk...
I would suspect the cause of this is actually the debug info, because DMD has some minor issues generating proper debug info if you are either in release mode, or...
Yes, 123 in that is the line in the original file where the mixin came from.
The thing is though, Mono-D's parser and completion engine is better in my experience than DCD's is.
Actually, @etcimon, [Orvid/TribesAscendSDK](https://github.com/Orvid/TribesAscendSDK) contains just over 245k lines of D code, and that would be longer if I didn't use a few mixins to shorten the generated code. It's 11mb...