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 don't know what the best way of defining this is, but it may even make sense to split up the entire import path into its constituent parts like so. This would match how java does packages in scip-java.
I guess the reasoning would be that you'd like to be able to do something like click on the modfile identifier, and go to the import string itself at the top of the file? Instead of going directly to the module?
I was actually trying to mimick gopls' semantic tokens, which mark the actual variable as a definition. That also lets us do neat stuff like checking for unreferenced variables in a package without needing to actually parse the language.
If you do an aliased import, we get a local definition:
When importing a package as a FQN we don't get a definition for the actual variable that is used inside the code:
Expected:
I don't know what the best way of defining this is, but it may even make sense to split up the entire import path into its constituent parts like so. This would match how java does packages in scip-java.
The text was updated successfully, but these errors were encountered: