You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The compilation server currently has a single initialized flag which governs the class path exploration. This works fine for single contexts, but misses information if there are multiple contexts involved.
As an example, starting the server with a Hello World program and then adding -lib flixel to the build will cause completion requests to miss the flixel packages and types.
We should instead track initialization status per-signature.
A related problem is the change of class paths without changing the signature. This is a rare case which only occurs by adding or removing explicit -cp arguments (because -lib comes with -D which changes signature). We already detect changed class paths, so this is a matter of unsetting the initialization status.
The text was updated successfully, but these errors were encountered:
The compilation server currently has a single
initialized
flag which governs the class path exploration. This works fine for single contexts, but misses information if there are multiple contexts involved.As an example, starting the server with a Hello World program and then adding
-lib flixel
to the build will cause completion requests to miss the flixel packages and types.We should instead track initialization status per-signature.
A related problem is the change of class paths without changing the signature. This is a rare case which only occurs by adding or removing explicit
-cp
arguments (because-lib
comes with-D
which changes signature). We already detect changed class paths, so this is a matter of unsetting the initialization status.The text was updated successfully, but these errors were encountered: