October 03
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.
October 04

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.