analyzer: rework path handling to simplify and reduce load #86
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The PR reworks path handling by using a
pathschild struct on theLanguageServer. vpaths will be set up during the language server setup process and become easily accessible throughout the session.This helps to remove things like calling the
compiler_path()function and calculating the vexe path on e.g. every request to a tool (like formatting on save). The same goes for repetitive calls ofvmodules_root()andvlib_root(). Instead, the paths are just available vials.paths.vexels.paths.vlib_rootls.paths.vmodules_root.