• Joseph (9/9) Oct 03 2017 Visual D has took 1/2 of my hair! Because intellisense is so
• Rainer Schuetze (17/26) Oct 03 2017 Sorry to hear Visual D affecting your hair. Unfortunately the D language...
• Brian Schott (3/4) Dec 06 2017 Agreed.
• Jacob Carlborg (7/11) Dec 07 2017 Yeah, that's why we have a Dub package for the DMD front end [1].

Joseph <JE342 gmail.com> writes:

Visual D has took 1/2 of my hair! Because intellisense is so 
broke, I cannot navigate my complex program easily, specially if 
I have forgot something. It would be really nice if at least find 
all reference or go to definition worked properly!  It seems that 
visual D is ignoring half of my project from being input as 
intellisense sources.

I'm not sure, but I compiled some of my code with the json tag 
and stuck it in the json directory visual d wants and some of my 
data seems to have intellisense.

Rainer Schuetze <r.sagitario gmx.de> writes:

On 03.10.2017 09:27, Joseph wrote:
 Visual D has took 1/2 of my hair! Because intellisense is so broke, I 
 cannot navigate my complex program easily, specially if I have forgot 
 something. It would be really nice if at least find all reference or go 
 to definition worked properly!  It seems that visual D is ignoring half 
 of my project from being input as intellisense sources.

Sorry to hear Visual D affecting your hair. Unfortunately the D language 
is rather difficult to implement. The semantic analysis is borrowed from 
Mono-D, with just a few additions done for Visual D: 
https://github.com/rainers/D_Parser. As far as I can tell it is still 
the best engine for IDE integration around.

The last couple of days I've been trying to use the dmd front end 
instead, but so far I've been unable to tame it from eating memory like 
crazy.

 
 I'm not sure, but I compiled some of my code with the json tag and stuck 
 it in the json directory visual d wants and some of my data seems to 
 have intellisense.

If the json files are generated as part of the build process, they are 
automatically included in the internal "database" (also visible in the 
object browser). No need to copy them into one of the predefined 
directories.

With respect to completion, the information in JSON files has the 
advantage that it is available before the proper imports are added for 
symbols to be found in the current scope. The disadvantage is that it 
has little information about scope to begin with, so only filters by name.

Brian Schott <briancschott gmail.com> writes:

On Wednesday, 4 October 2017 at 06:39:14 UTC, Rainer Schuetze 
wrote:
 Unfortunately the D language is rather difficult to implement.

Agreed.

Jacob Carlborg <doob me.com> writes:

On 2017-12-07 07:18, Brian Schott wrote:
 On Wednesday, 4 October 2017 at 06:39:14 UTC, Rainer Schuetze wrote:
 Unfortunately the D language is rather difficult to implement.

 
 Agreed.

Yeah, that's why we have a Dub package for the DMD front end [1]. 
Unfortunately it only contains the lexer and parser so far. Hopefully we 
can get the semantic analyzer into the Dub package as well.

[1] http://code.dlang.org/packages/dmd

-- 
/Jacob Carlborg