-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{integer}..unresolved_ident suggests field access #131471
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
A-suggestion-diagnostics
Area: Suggestions generated by the compiler applied by `cargo fix`
D-invalid-suggestion
Diagnostics: A structured suggestion resulting in incorrect code.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
I'm working on this |
hirschenberger
added a commit
to hirschenberger/rust
that referenced
this issue
Oct 11, 2024
Fixes rust-lang#131471 by checking if the range-start is a literal.
hirschenberger
added a commit
to hirschenberger/rust
that referenced
this issue
Oct 12, 2024
Fixes rust-lang#131471 by checking if the range-start is a literal.
hirschenberger
added a commit
to hirschenberger/rust
that referenced
this issue
Oct 12, 2024
Fixes rust-lang#131471 by checking if the range-start is a literal.
hirschenberger
added a commit
to hirschenberger/rust
that referenced
this issue
Oct 18, 2024
Fixes rust-lang#131471 by checking if the range-start is a literal.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Oct 18, 2024
…errors Fix range misleading field access Fixes rust-lang#131471 by checking if the range-start is a literal.
workingjubilee
added a commit
to workingjubilee/rustc
that referenced
this issue
Oct 19, 2024
…errors Fix range misleading field access Fixes rust-lang#131471 by checking if the range-start is a literal.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Oct 19, 2024
…errors Fix range misleading field access Fixes rust-lang#131471 by checking if the range-start is a literal.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Oct 19, 2024
…errors Fix range misleading field access Fixes rust-lang#131471 by checking if the range-start is a literal.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Oct 19, 2024
…errors Fix range misleading field access Fixes rust-lang#131471 by checking if the range-start is a literal.
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 19, 2024
Rollup merge of rust-lang#131537 - hirschenberger:master, r=compiler-errors Fix range misleading field access Fixes rust-lang#131471 by checking if the range-start is a literal.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
A-suggestion-diagnostics
Area: Suggestions generated by the compiler applied by `cargo fix`
D-invalid-suggestion
Diagnostics: A structured suggestion resulting in incorrect code.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Code
Current output
Desired output
Rationale and extra context
Since integer literals do not have fields, it's odd to suggest field access.
It just confuses the user, rather than helping.
Other cases
No response
Rust Version
Anything else?
No response
The text was updated successfully, but these errors were encountered: