Support raw_ref_op's raw reference operator#4648
Merged
bors[bot] merged 1 commit intorust-lang:masterfrom May 29, 2020
Merged
Conversation
Member
|
LGTM, @matklad might want to take a short look at the parser code though. |
Contributor
|
bors r+ |
Contributor
github-actions bot
pushed a commit
that referenced
this pull request
Jan 8, 2026
Use the dummy codegen backend
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
3 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.
Fixes #4642.
This syntax (and its semantics) are implemented in rustc behind the
raw_ref_opfeature.It is not entirely clear whether this is the syntax that will become stable, but it seems like rust-analyzer must still support this unstable syntax to support future stable rust.
Also fixes a random inference failure involving a direct coercion from
&[T, _]to*const [T].