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
I believe right now we are loading everything that is in the Julia environment that we pass to the SymServer. So if we have an env and the current working folder in VS Code is deved into that env, then SymServer will load the content of the package that we are currently editing.
It seems to me that in general we don't want to load anything that is somewhere in the folder hierarchy under any of the root folders of the workspace at all, after all the content of those files will be obtained from parsing etc., right? I.e. the philosophy should be that SymServer only loads stuff that is outside of the workspace that is currently edited in VS Code.
Broadly -yes, this fits in with the solution being discussed on the LOAD_PATH issue. One caveat - the inability of StaticLint to pick up hard to find bindings (e.g. macro gen'ed or eval'ed stuff) will become more obvious in some cases.
I believe right now we are loading everything that is in the Julia environment that we pass to the SymServer. So if we have an env and the current working folder in VS Code is
deved
into that env, then SymServer will load the content of the package that we are currently editing.It seems to me that in general we don't want to load anything that is somewhere in the folder hierarchy under any of the root folders of the workspace at all, after all the content of those files will be obtained from parsing etc., right? I.e. the philosophy should be that SymServer only loads stuff that is outside of the workspace that is currently edited in VS Code.
@ZacLN, does that sound right to you?
The text was updated successfully, but these errors were encountered: