rust/tests/ui/lifetimes/lifetime-errors/ex3-both-anon-regions-both-are-structs.stderr

error: lifetime may not live long enough
  --> $DIR/ex3-both-anon-regions-both-are-structs.rs:6:5
   |
LL | fn foo(mut x: Vec<Ref>, y: Ref) {
   |        -----            - has type `Ref<'1>`
   |        |
   |        has type `Vec<Ref<'2>>`
LL |     x.push(y);
   |     ^^^^^^^^^ argument requires that `'1` must outlive `'2`

error: aborting due to previous error
Change compare mode to use -Zborrowck=mir 2019-01-27 05:03:21 -06:00			`error: lifetime may not live long enough`
Fully stabilize NLL 2022-04-01 12:13:25 -05:00			`--> $DIR/ex3-both-anon-regions-both-are-structs.rs:6:5`
Change compare mode to use -Zborrowck=mir 2019-01-27 05:03:21 -06:00			`\|`
			`LL \| fn foo(mut x: Vec<Ref>, y: Ref) {`
			\| ----- - has type `Ref<'1>`
			`\| \|`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 02:40:56 -05:00			\| has type `Vec<Ref<'2>>`
Change compare mode to use -Zborrowck=mir 2019-01-27 05:03:21 -06:00			`LL \| x.push(y);`
			\| ^^^^^^^^^ argument requires that `'1` must outlive `'2`

			`error: aborting due to previous error`