rust/tests/ui/lifetimes/lifetime-errors/ex2b-push-no-existing-names.stderr

error: lifetime may not live long enough
  --> $DIR/ex2b-push-no-existing-names.rs:6:5
   |
LL | fn foo(x: &mut Vec<Ref<i32>>, y: Ref<i32>) {
   |        -                      - has type `Ref<'1, i32>`
   |        |
   |        has type `&mut Vec<Ref<'2, i32>>`
LL |     x.push(y);
   |     ^^^^^^^^^ argument requires that `'1` must outlive `'2`
   |
   = note: requirement occurs because of a mutable reference to `Vec<Ref<'_, i32>>`
   = note: mutable references are invariant over their type parameter
   = help: see <https://doc.rust-lang.org/nomicon/subtyping.html> for more information about variance
help: consider introducing a named lifetime parameter
   |
LL | fn foo<'a>(x: &mut Vec<Ref<'a, i32>>, y: Ref<'a, i32>) {
   |       ++++                 +++               +++

error: aborting due to 1 previous error
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00			`error: lifetime may not live long enough`
Fully stabilize NLL 2022-04-01 13:13:25 -04:00			`--> $DIR/ex2b-push-no-existing-names.rs:6:5`
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00			`\|`
			`LL \| fn foo(x: &mut Vec<Ref<i32>>, y: Ref<i32>) {`
			\| - - has type `Ref<'1, i32>`
			`\| \|`
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 10:40:56 +03:00			\| has type `&mut Vec<Ref<'2, i32>>`
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00			`LL \| x.push(y);`
			\| ^^^^^^^^^ argument requires that `'1` must outlive `'2`
Suggest setting lifetime in borrowck error involving types with elided lifetimes ``` error: lifetime may not live long enough --> $DIR/ex3-both-anon-regions-both-are-structs-2.rs:7:5 \| LL \| fn foo(mut x: Ref, y: Ref) { \| ----- - has type `Ref<'_, '1>` \| \| \| has type `Ref<'_, '2>` LL \| x.b = y.b; \| ^^^^^^^^^ assignment requires that `'1` must outlive `'2` \| help: consider introducing a named lifetime parameter \| LL \| fn foo<'a>(mut x: Ref<'a, 'a>, y: Ref<'a, 'a>) { \| ++++ ++++++++ ++++++++ ``` As can be seen above, it currently doesn't try to compare the `ty::Ty` lifetimes that diverged vs the `hir::Ty` to correctly suggest the following ``` help: consider introducing a named lifetime parameter \| LL \| fn foo<'a>(mut x: Ref<'_, 'a>, y: Ref<'_, 'a>) { \| ++++ ++++++++ ++++++++ ``` but I believe this to still be an improvement over the status quo. CC #40990. 2024-05-03 21:42:34 +00:00			`\|`
`best_blame_constraint`: don't filter constraints by sup SCC The SCCs of the region graph are not a reliable heuristic to use for blaming an interesting constraint for diagnostics. For region errors, if the outlived region is `'static`, or the involved types are invariant in their lifetiems, there will be cycles in the constraint graph containing both the target region and the most interesting constraints to blame. To get better diagnostics in these cases, this commit removes that heuristic. 2024-12-04 03:19:03 -08:00			= note: requirement occurs because of a mutable reference to `Vec<Ref<'_, i32>>`
			`= note: mutable references are invariant over their type parameter`
			`= help: see <https://doc.rust-lang.org/nomicon/subtyping.html> for more information about variance`
Suggest setting lifetime in borrowck error involving types with elided lifetimes ``` error: lifetime may not live long enough --> $DIR/ex3-both-anon-regions-both-are-structs-2.rs:7:5 \| LL \| fn foo(mut x: Ref, y: Ref) { \| ----- - has type `Ref<'_, '1>` \| \| \| has type `Ref<'_, '2>` LL \| x.b = y.b; \| ^^^^^^^^^ assignment requires that `'1` must outlive `'2` \| help: consider introducing a named lifetime parameter \| LL \| fn foo<'a>(mut x: Ref<'a, 'a>, y: Ref<'a, 'a>) { \| ++++ ++++++++ ++++++++ ``` As can be seen above, it currently doesn't try to compare the `ty::Ty` lifetimes that diverged vs the `hir::Ty` to correctly suggest the following ``` help: consider introducing a named lifetime parameter \| LL \| fn foo<'a>(mut x: Ref<'_, 'a>, y: Ref<'_, 'a>) { \| ++++ ++++++++ ++++++++ ``` but I believe this to still be an improvement over the status quo. CC #40990. 2024-05-03 21:42:34 +00:00			`help: consider introducing a named lifetime parameter`
			`\|`
			`LL \| fn foo<'a>(x: &mut Vec<Ref<'a, i32>>, y: Ref<'a, i32>) {`
			`\| ++++ +++ +++`
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00