-
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
Extend E0623 for named conflicts #43882
Comments
Here's the code I pushed into a local branch. |
Status:The check for
Logs are
|
@nikomatsakis
I've confirmed with @arielb1 that this is the correct example for the case but it doesn't seem to trigger the |
Could you add in which case this code will improve the current rustc output please? (Put a code with the current output and then the improved one.) It'll help us to understand what you want to do. |
@GuillaumeGomez here is the example
Current output
New output
|
Extend E0623 for LateBound and EarlyBound Regions This is a fix for #43882 ``` fn foo<'a,'b>(x: &mut Vec<&'a u8>, y: &'b u8) { x.push(y); } ``` now gives ``` error[E0623]: lifetime mismatch --> $DIR/ex3-both-anon-regions-latebound-regions.rs:12:12 | 11 | fn foo<'a,'b>(x: &mut Vec<&'a u8>, y: &'b u8) { | ------ ------ these two types are declared with different lifetimes... 12 | x.push(y); | ^ ...but data from `y` flows into `x` here ``` cc @nikomatsakis @arielb1 Please ignore the second commit. It will be merged in a separate PR.
In the process of doing it for structs now |
|
@gaurikholkar, are there outstanding tasks for this issue? |
Nope. @estebank updated the title. |
Sooo, can this be closed? |
I guess so. |
Adding changes for
rl::Region::EarlyBound
andrl::Region::LateBound
for references.Still looking for good examples
cc @nikomatsakis @estebank @GuillaumeGomez @arielb1
The text was updated successfully, but these errors were encountered: