Don't suggest adding let in certain if conditions
#97856
Merged
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
rustbot
added
the
T-compiler
|
(rust-highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
the
S-waiting-on-review
|
r? @estebank |
estebank
approved these changes
Jun 8, 2022
Comment on lines
+1
to
+13
| error: `let` expressions are not supported here | ||
| --> $DIR/bad-if-let-suggestion.rs:5:8 | ||
| | | ||
| LL | if let x = 1 && i = 2 {} | ||
| | ^^^^^^^^^ | ||
| | | ||
| = note: only supported directly in conditions of `if` and `while` expressions | ||
|
|
||
| error[E0425]: cannot find value `i` in this scope | ||
| --> $DIR/bad-if-let-suggestion.rs:5:21 | ||
| | | ||
| LL | if let x = 1 && i = 2 {} | ||
| | ^ not found in this scope |
There was a problem hiding this comment.
This error isn't as good as it could be :(
There was a problem hiding this comment.
yeah i left a fixme
Comment on lines
+51
to
+64
| error[E0658]: `let` expressions in this position are unstable | ||
| --> $DIR/bad-if-let-suggestion.rs:5:8 | ||
| | | ||
| LL | if let x = 1 && i = 2 {} | ||
| | ^^^^^^^^^ | ||
| | | ||
| = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information | ||
| = help: add `#![feature(let_chains)]` to the crate attributes to enable | ||
|
|
||
| error[E0308]: mismatched types | ||
| --> $DIR/bad-if-let-suggestion.rs:5:8 | ||
| | | ||
| LL | if let x = 1 && i = 2 {} | ||
| | ^^^^^^^^^^^^^^^^^^ expected `bool`, found `()` |
There was a problem hiding this comment.
It'd be nice if all the errors pointing at line 5 (these plus the ones highlighted above) ended up being only one. Particularly the "let not supported here" and "let expressions are unstable" seem to be quite redundant.
There was a problem hiding this comment.
yeah, the problem is that they all happen in different stages :( so it's really hard to suppress further ones
There was a problem hiding this comment.
Oh, for sure. I wasn't suggesting doing it in this PR, only mentioning what follow up work that I'd like to get to at some point.
|
@bors r+ |
|
📌 Commit 2ae1ec9 has been approved by |
bors
added
S-waiting-on-bors
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Jun 8, 2022
…piler-errors Rollup of 9 pull requests Successful merges: - rust-lang#97557 (Fix indices and remove some unwraps in arg mismatch algorithm) - rust-lang#97830 (Add std::alloc::set_alloc_error_hook example) - rust-lang#97856 (Don't suggest adding `let` in certain `if` conditions) - rust-lang#97857 (Suggest escaping `box` as identifier) - rust-lang#97871 (Suggest using `iter()` or `into_iter()` for `Vec`) - rust-lang#97882 (Add regresion test for rust-lang#67498) - rust-lang#97883 (Remove `ignore-compare-mode-nll` annotations from tests) - rust-lang#97891 (Update books) - rust-lang#97894 (Fix polonius compare mode.) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
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.
Avoid being too eager to suggest
letin anifcondition with an=, namely when the LHS of the=isn't even valid as a pattern (to a first degree approximation).This heustic I came up with kinda sucks. Let me know if it needs to be refined.