https://issues.dlang.org/show_bug.cgi?id=20255
--- Comment #3 from berni44 <[email protected]> --- Maybe this is a Dlangide bug which is allready fixed? [1] The strange thing is, that the fix happend before the issue was reported and according to the attached log the version of Dlangide is one, where the issue was allready fixed. [1] https://github.com/buggins/dlangide/issues/398 --
