-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Suggest solutions for fn foo(&foo: Foo)
#38605
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
5598f35
Suggest solutions for `fn foo(&foo: Foo)`
estebank f2dd75c
review comments
estebank 563ecc1
add test case
estebank 59d7d4c
only emit suggestion to move `&` if the inner pattern is a binding
nikomatsakis d723e02
update test case to include `fn(&&u32: Foo)`
nikomatsakis File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
// Copyright 2017 The Rust Project Developers. See the COPYRIGHT | ||
// file at the top-level directory of this distribution and at | ||
// http://rust-lang.org/COPYRIGHT. | ||
// | ||
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or | ||
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license | ||
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your | ||
// option. This file may not be copied, modified, or distributed | ||
// except according to those terms. | ||
#![feature(slice_patterns)] | ||
|
||
|
||
struct Foo { | ||
} | ||
|
||
fn foo(&foo: Foo) { | ||
} | ||
|
||
fn bar(foo: Foo) { | ||
} | ||
|
||
fn qux(foo: &Foo) { | ||
} | ||
|
||
fn zar(&foo: &Foo) { | ||
} | ||
|
||
fn agh(&&bar: &u32) { | ||
} | ||
|
||
fn bgh(&&bar: u32) { | ||
} | ||
|
||
fn ugh(&[bar]: &u32) { | ||
} | ||
|
||
fn main() {} |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
error[E0308]: mismatched types | ||
--> $DIR/issue-38371.rs:16:8 | ||
| | ||
16 | fn foo(&foo: Foo) { | ||
| ^^^^ expected struct `Foo`, found reference | ||
| | ||
= note: expected type `Foo` | ||
= note: found type `&_` | ||
= help: did you mean `foo: &Foo`? | ||
|
||
error[E0308]: mismatched types | ||
--> $DIR/issue-38371.rs:28:9 | ||
| | ||
28 | fn agh(&&bar: &u32) { | ||
| ^^^^ expected u32, found reference | ||
| | ||
= note: expected type `u32` | ||
= note: found type `&_` | ||
|
||
error[E0308]: mismatched types | ||
--> $DIR/issue-38371.rs:31:8 | ||
| | ||
31 | fn bgh(&&bar: u32) { | ||
| ^^^^^ expected u32, found reference | ||
| | ||
= note: expected type `u32` | ||
= note: found type `&_` | ||
|
||
error[E0529]: expected an array or slice, found `u32` | ||
--> $DIR/issue-38371.rs:34:9 | ||
| | ||
34 | fn ugh(&[bar]: &u32) { | ||
| ^^^^^ pattern cannot match with input type `u32` | ||
|
||
error: aborting due to 4 previous errors | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we have to fix this here necessarily, but I feel like these
note:
messages are kind of distracting from thehelp
, which is more likely to be of use. But I'm not sure how to fix without doing potentially more harm than good, so let's leave as is.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a while I've been thinking wether it would make sense to make the
expected
/found
notes a first class comment, so that these errors would look closer toIf you feel there'd be value on that, I could create an issue and start a PR for it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that looks better
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opened issue #38901 and PR #38902 for this.