mirror of
https://github.com/rust-lang/rust.git
synced 2024-12-02 03:33:59 +00:00
e62599f856
This makes a small change as requested in code review, such that if there's
ambiguity in the self lifetime, we avoid lifetime elision entirely instead of
considering using lifetimes from any of the other parameters.
For example,
impl Something {
fn method(self: &Box<&Self>, something_else: &u32) -> &u32 { ... }
}
in standard Rust would have assumed the return lifetime was that of &Self;
with this PR prior to this commit would have chosen the lifetime of
'something_else', and after this commit would give an error message explaining
that the lifetime is ambiguous.
28 lines
1.4 KiB
Plaintext
28 lines
1.4 KiB
Plaintext
error[E0106]: missing lifetime specifier
|
|
--> $DIR/ref-self-multi.rs:18:56
|
|
|
|
|
LL | fn ref_box_ref_Self(self: &Box<&Self>, f: &u32) -> &u32 {
|
|
| ----------- ---- ^ expected named lifetime parameter
|
|
|
|
|
= help: this function's return type contains a borrowed value, but the signature does not say whether it is borrowed from one of `self`'s 2 lifetimes or `f`
|
|
help: consider introducing a named lifetime parameter
|
|
|
|
|
LL | fn ref_box_ref_Self<'a>(self: &'a Box<&'a Self>, f: &'a u32) -> &'a u32 {
|
|
| ++++ ++ ++ ++ ++
|
|
|
|
error[E0106]: missing lifetime specifier
|
|
--> $DIR/ref-self-multi.rs:23:63
|
|
|
|
|
LL | fn ref_wrap_ref_Self(self: &Wrap<&Self, u32>, f: &u32) -> &u32 {
|
|
| ----------------- ---- ^ expected named lifetime parameter
|
|
|
|
|
= help: this function's return type contains a borrowed value, but the signature does not say whether it is borrowed from one of `self`'s 2 lifetimes or `f`
|
|
help: consider introducing a named lifetime parameter
|
|
|
|
|
LL | fn ref_wrap_ref_Self<'a>(self: &'a Wrap<&'a Self, u32>, f: &'a u32) -> &'a u32 {
|
|
| ++++ ++ ++ ++ ++
|
|
|
|
error: aborting due to 2 previous errors
|
|
|
|
For more information about this error, try `rustc --explain E0106`.
|