Avoid reliance on bazel-bin for rust-analyzer IDE setup#4112
Merged
Conversation
UebelAndre
force-pushed
the
rust-analyzer
branch
6 times, most recently
from
9436924 to
ef00814
Compare
UebelAndre
force-pushed
the
rust-analyzer
branch
7 times, most recently
from
20eee7d to
321faf2
Compare
UebelAndre
force-pushed
the
rust-analyzer
branch
from
321faf2 to
7d96ebb
Compare
illicitonion
approved these changes
Jun 27, 2026
This file contains hidden or 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
2 participants
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 change removes any reliance
setupplaced onbazel-binas it's an unreliable path. Instead binaries likeflycheckare installed into the setup directory and the output_base is used to identify rust-analyzer and the sysroot.