Somtimes completion proposals takes too long to complete

Well, we're always looking to improve the performance, but this is often hard to considering the model Descent is built on. Here are some things to try in the meantime:

1. Are you using files with public imports? Importing a ".all" file will force every file imported to be front-end-compiled. 2. Are you using any heavy CTFE or recursive templates? That tends to bog things down in the frontend. 3. Does it take >30 seconds to compile in DMD?

If none of that is true and you're still having serious speed problems, it may be a caching issue or something else easily cleared up. Please send an example or point us to a repository if you can, since that'll help us determine what pieces of code can take unreasonable amounts of time.

I have this code:

import dwt.widgets.Display;
import dwt.display.Shell;

void main ()
{
    Dis...
}

I start the code completion after the three dots. None of the above imports have any public imports. One is around 2300 lines of code and the other around 4500. I have the whole dsss\include\d in "Compiler system libraries". That example takes under 5 seconds to compile.

I tested that same code, and it showed me the proposals right away, so it might happen randomly. Anyway, I'll completely rewrite the semantic analysis for the next version since I found out it's not quite what JDT does.