build: use different target dir for rust-analyzer to prevent thrashing with cargo #1460
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
|
Hmm, this might use up more disk space for @jhellerstein |
MingweiSamuel
force-pushed
the
ra-thrashing
branch
from
655b80e to
cf05887
Compare
|
Wouldn't disabling the python feature be sufficient to prevent thrashing? |
|
Not on my windows machine, both builds still invalidated each other |
|
Maybe we should inspect all our |
|
Just changed it on my user vscode settings.json on my windows machine. |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Might only be a problem on windows?
Edit: seems to only be windows