| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2024-05-22 | Ambiguous Self lifetimes: don't elide. | Adrian Taylor | -0/+7 | |
| struct Concrete(u32); impl Concrete { fn m(self: &Box<Self>) -> &u32 { &self.0 } } resulted in a confusing error. impl Concrete { fn n(self: &Box<&Self>) -> &u32 { &self.0 } } resulted in no error or warning, despite apparent ambiguity over the elided lifetime. This commit changes two aspects of the behavior. Previously, when examining the self type, we considered lifetimes only if they were immediately adjacent to Self. We now consider lifetimes anywhere in the self type. Secondly, if more than one lifetime is discovered in the self type, we disregard it as a possible lifetime elision candidate. This is a compatibility break, and in fact has required some changes to tests which assumed the earlier behavior. Fixes https://github.com/rust-lang/rust/issues/117715 | ||||
| 2024-05-17 | Run `rustfmt` on modified tests | Esteban Küber | -2/+4 | |
| 2024-05-17 | Account for owning item lifetimes in suggestion and annotate tests as ↵ | Esteban Küber | -2/+3 | |
| `run-rustfix` ``` error: lifetime may not live long enough --> $DIR/lt-ref-self.rs:12:9 | LL | fn ref_self(&self, f: &u32) -> &u32 { | - - let's call the lifetime of this reference `'1` | | | let's call the lifetime of this reference `'2` LL | f | ^ method was supposed to return data with lifetime `'2` but it is returning data with lifetime `'1` | help: consider introducing a named lifetime parameter and update trait if needed | LL | fn ref_self<'b>(&'b self, f: &'b u32) -> &'b u32 { | ++++ ++ ++ ++ ``` | ||||
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -0/+58 | |
