rust/tests/ui/regions/region-invariant-static-error-reporting.stderr

error: lifetime may not live long enough
  --> $DIR/region-invariant-static-error-reporting.rs:16:9
   |
LL | fn unify<'a>(x: Option<Invariant<'a>>, f: fn(Invariant<'a>)) {
   |          -- lifetime `'a` defined here
...
LL |         mk_static()
   |         ^^^^^^^^^^^ assignment requires that `'a` must outlive `'static`
   |
   = note: requirement occurs because of the type `Invariant<'_>`, which makes the generic argument `'_` invariant
   = note: the struct `Invariant<'a>` is invariant over the parameter `'a`
   = help: see <https://doc.rust-lang.org/nomicon/subtyping.html> for more information about variance

error: aborting due to 1 previous error
`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			`error: lifetime may not live long enough`
			`--> $DIR/region-invariant-static-error-reporting.rs:16:9`
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00			`\|`
			`LL \| fn unify<'a>(x: Option<Invariant<'a>>, f: fn(Invariant<'a>)) {`
`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			\| -- lifetime `'a` defined here
			`...`
			`LL \| mk_static()`
			\| ^^^^^^^^^^^ assignment requires that `'a` must outlive `'static`
Refactor variance diagnostics to work with more types Instead of special-casing mutable pointers/references, we now support general generic types (currently, we handle `ty::Ref`, `ty::RawPtr`, and `ty::Adt`) When a `ty::Adt` is involved, we show an additional note explaining which of the type's generic parameters is invariant (e.g. the `T` in `Cell<T>`). Currently, we don't explain why a particular generic parameter ends up becoming invariant. In the general case, this could require printing a long 'backtrace' of types, so doing this would be more suitable for a follow-up PR. We still only handle the case where our variance switches to `ty::Invariant`. 2021-09-27 20:22:44 -05:00			`\|`
Format invariance notes with backticks 2022-04-02 15:32:39 -07:00			= note: requirement occurs because of the type `Invariant<'_>`, which makes the generic argument `'_` invariant
			= note: the struct `Invariant<'a>` is invariant over the parameter `'a`
Refactor variance diagnostics to work with more types Instead of special-casing mutable pointers/references, we now support general generic types (currently, we handle `ty::Ref`, `ty::RawPtr`, and `ty::Adt`) When a `ty::Adt` is involved, we show an additional note explaining which of the type's generic parameters is invariant (e.g. the `T` in `Cell<T>`). Currently, we don't explain why a particular generic parameter ends up becoming invariant. In the general case, this could require printing a long 'backtrace' of types, so doing this would be more suitable for a follow-up PR. We still only handle the case where our variance switches to `ty::Invariant`. 2021-09-27 20:22:44 -05:00			`= help: see <https://doc.rust-lang.org/nomicon/subtyping.html> for more information about variance`
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