-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Print ParamTy span when accessing a field (#52082) #64852
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
Merged
Merged
Changes from 1 commit
Commits
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 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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
// Fix issue 52082: Confusing error if accidentially defining a type paramter with the same name as | ||
estebank marked this conversation as resolved.
Show resolved
Hide resolved
|
||
// an existing type | ||
// | ||
// To this end, make sure that when trying to retrieve a field of a (reference to) type parameter, | ||
// rustc points to the point where the parameter was defined. | ||
#[derive(Debug)] | ||
struct Point | ||
{ | ||
x: i32, | ||
y: i32 | ||
} | ||
|
||
impl Point | ||
{ | ||
fn add(a: &Point, b: &Point) -> Point | ||
{ | ||
Point {x: a.x + b.x, y: a.y + b.y} | ||
} | ||
} | ||
|
||
trait Eq | ||
{ | ||
fn equals_ref<T>(a: &T, b: &T) -> bool; | ||
fn equals_val<T>(a: T, b: T) -> bool; | ||
} | ||
|
||
impl Eq for Point | ||
{ | ||
fn equals_ref<Point>(a: &Point, b: &Point) -> bool | ||
{ | ||
a.x == b.x && a.y == b.y //~ ERROR no field `x` on type `&Point` [E0609] | ||
//~|ERROR no field `x` on type `&Point` [E0609] | ||
//~|ERROR no field `y` on type `&Point` [E0609] | ||
//~|ERROR no field `y` on type `&Point` [E0609] | ||
} | ||
|
||
fn equals_val<Point>(a: Point, b: Point) -> bool | ||
{ | ||
a.x == b.x && a.y == b.y //~ ERROR no field `x` on type `Point` [E0609] | ||
//~|ERROR no field `x` on type `Point` [E0609] | ||
//~|ERROR no field `y` on type `Point` [E0609] | ||
//~|ERROR no field `y` on type `Point` [E0609] | ||
} | ||
} | ||
|
||
fn main() | ||
{ | ||
let p1 = Point {x: 0, y: 10}; | ||
let p2 = Point {x: 20, y: 42}; | ||
println!("{:?}", Point::add(&p1, &p2)); | ||
println!("p1: {:?}, p2: {:?}", p1, p2); | ||
println!("&p1 == &p2: {:?}", Point::equals_ref(&p1, &p2)); | ||
println!("p1 == p2: {:?}", Point::equals_val(p1, p2)); | ||
} |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,99 @@ | ||
error[E0609]: no field `x` on type `&Point` | ||
--> $DIR/issue-52082.rs:31:11 | ||
| | ||
LL | a.x == b.x && a.y == b.y | ||
| ^ | ||
| | ||
note: Type parameter 'Point' was declared here | ||
--> $DIR/issue-52082.rs:29:19 | ||
| | ||
LL | fn equals_ref<Point>(a: &Point, b: &Point) -> bool | ||
| ^^^^^ | ||
|
||
error[E0609]: no field `x` on type `&Point` | ||
--> $DIR/issue-52082.rs:31:18 | ||
| | ||
LL | a.x == b.x && a.y == b.y | ||
| ^ | ||
| | ||
note: Type parameter 'Point' was declared here | ||
--> $DIR/issue-52082.rs:29:19 | ||
| | ||
LL | fn equals_ref<Point>(a: &Point, b: &Point) -> bool | ||
| ^^^^^ | ||
|
||
error[E0609]: no field `y` on type `&Point` | ||
--> $DIR/issue-52082.rs:31:25 | ||
| | ||
LL | a.x == b.x && a.y == b.y | ||
| ^ | ||
| | ||
note: Type parameter 'Point' was declared here | ||
--> $DIR/issue-52082.rs:29:19 | ||
| | ||
LL | fn equals_ref<Point>(a: &Point, b: &Point) -> bool | ||
| ^^^^^ | ||
|
||
error[E0609]: no field `y` on type `&Point` | ||
--> $DIR/issue-52082.rs:31:32 | ||
| | ||
LL | a.x == b.x && a.y == b.y | ||
| ^ | ||
| | ||
note: Type parameter 'Point' was declared here | ||
--> $DIR/issue-52082.rs:29:19 | ||
| | ||
LL | fn equals_ref<Point>(a: &Point, b: &Point) -> bool | ||
| ^^^^^ | ||
|
||
error[E0609]: no field `x` on type `Point` | ||
--> $DIR/issue-52082.rs:39:11 | ||
| | ||
LL | a.x == b.x && a.y == b.y | ||
| ^ | ||
| | ||
note: Type parameter 'Point' was declared here | ||
--> $DIR/issue-52082.rs:37:19 | ||
| | ||
LL | fn equals_val<Point>(a: Point, b: Point) -> bool | ||
| ^^^^^ | ||
|
||
error[E0609]: no field `x` on type `Point` | ||
--> $DIR/issue-52082.rs:39:18 | ||
| | ||
LL | a.x == b.x && a.y == b.y | ||
| ^ | ||
| | ||
note: Type parameter 'Point' was declared here | ||
--> $DIR/issue-52082.rs:37:19 | ||
| | ||
LL | fn equals_val<Point>(a: Point, b: Point) -> bool | ||
| ^^^^^ | ||
|
||
error[E0609]: no field `y` on type `Point` | ||
--> $DIR/issue-52082.rs:39:25 | ||
| | ||
LL | a.x == b.x && a.y == b.y | ||
| ^ | ||
| | ||
note: Type parameter 'Point' was declared here | ||
--> $DIR/issue-52082.rs:37:19 | ||
| | ||
LL | fn equals_val<Point>(a: Point, b: Point) -> bool | ||
| ^^^^^ | ||
|
||
error[E0609]: no field `y` on type `Point` | ||
--> $DIR/issue-52082.rs:39:32 | ||
| | ||
LL | a.x == b.x && a.y == b.y | ||
| ^ | ||
| | ||
note: Type parameter 'Point' was declared here | ||
--> $DIR/issue-52082.rs:37:19 | ||
| | ||
LL | fn equals_val<Point>(a: Point, b: Point) -> bool | ||
| ^^^^^ | ||
|
||
error: aborting due to 8 previous errors | ||
|
||
For more information about this error, try `rustc --explain E0609`. |
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.
Uh oh!
There was an error while loading. Please reload this page.