Automatically import vstd and builtin #9
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
|
Would it make sense to apply those commits to #27 ? I did a rebase to the most recent rust-analyzer there (or well as of June 25) -- or are those commits already in there? |
|
These changes are incomplete, so I don't think we want to merge these into the latest rebase now. |
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.
This PR is to automatically import Verus' vstd(verified std) and builtin without the user's guide.
Currently Verus uses "pervasive" which will be replaced by "vstd", and we have the user to generated a symlink to the pervasive in the project's "src" directory. This was because "pervasive" was a module rather than a crate. As vstd becomes a separate crate, this PR changes verus-analyzer to index vstd crate when it index std crate in the startup.