mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1e5b2da94b
rust/tests/ui/nll/ty-outlives/projection-no-regions-fn.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

32 lines
1.3 KiB
Plaintext
Raw Normal View History

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
error[E0309]: the associated type `<T as Iterator>::Item` may not live long enough
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/projection-no-regions-fn.rs:13:5
move some parts of liveness to happen during type checking This allows us to re-use the `normalize` method on `TypeCheck`, which is important since normalization may create fresh region variables. This is not an ideal solution, though, since the current representation of "liveness constraints" (a vector of (region, point) pairs) is rather inefficient. Could do somewhat better by converting to indices, but it'd still be less good than the older code. Unclear how important this is.
2017-12-03 12:14:36 -06:00
|
always show and explain sub region
2023-09-17 09:32:02 -05:00
LL | fn no_region<'a, T>(mut x: T) -> Box<dyn Anything + 'a>
| -- the associated type `<T as Iterator>::Item` must be valid for the lifetime `'a` as defined here...
...
Update UI tests
2018-02-22 18:42:32 -06:00
LL | Box::new(x.next())
improve the suggestion of generic_bound_failure
2023-09-07 20:35:51 -05:00
| ^^^^^^^^^^^^^^^^^^ ...so that the type `<T as Iterator>::Item` will meet its required lifetime bounds
use `report_generic_bound_failure` when we can in the compiler
2017-12-19 10:12:56 -06:00
|
remove trailing dots
2023-10-08 05:06:17 -05:00
help: consider adding an explicit lifetime bound
improve the suggestion of generic_bound_failure
2023-09-07 20:35:51 -05:00
|
LL | T: Iterator, <T as Iterator>::Item: 'a
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~
move some parts of liveness to happen during type checking This allows us to re-use the `normalize` method on `TypeCheck`, which is important since normalization may create fresh region variables. This is not an ideal solution, though, since the current representation of "liveness constraints" (a vector of (region, point) pairs) is rather inefficient. Could do somewhat better by converting to indices, but it'd still be less good than the older code. Unclear how important this is.
2017-12-03 12:14:36 -06:00
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
error[E0309]: the associated type `<T as Iterator>::Item` may not live long enough
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/projection-no-regions-fn.rs:28:5
move some parts of liveness to happen during type checking This allows us to re-use the `normalize` method on `TypeCheck`, which is important since normalization may create fresh region variables. This is not an ideal solution, though, since the current representation of "liveness constraints" (a vector of (region, point) pairs) is rather inefficient. Could do somewhat better by converting to indices, but it'd still be less good than the older code. Unclear how important this is.
2017-12-03 12:14:36 -06:00
|
always show and explain sub region
2023-09-17 09:32:02 -05:00
LL | fn wrong_region<'a, 'b, T>(mut x: T) -> Box<dyn Anything + 'a>
| -- the associated type `<T as Iterator>::Item` must be valid for the lifetime `'a` as defined here...
...
Update UI tests
2018-02-22 18:42:32 -06:00
LL | Box::new(x.next())
improve the suggestion of generic_bound_failure
2023-09-07 20:35:51 -05:00
| ^^^^^^^^^^^^^^^^^^ ...so that the type `<T as Iterator>::Item` will meet its required lifetime bounds
|
remove trailing dots
2023-10-08 05:06:17 -05:00
help: consider adding an explicit lifetime bound
use `report_generic_bound_failure` when we can in the compiler
2017-12-19 10:12:56 -06:00
|
improve the suggestion of generic_bound_failure
2023-09-07 20:35:51 -05:00
LL | T: 'b + Iterator, <T as Iterator>::Item: 'a
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~
move some parts of liveness to happen during type checking This allows us to re-use the `normalize` method on `TypeCheck`, which is important since normalization may create fresh region variables. This is not an ideal solution, though, since the current representation of "liveness constraints" (a vector of (region, point) pairs) is rather inefficient. Could do somewhat better by converting to indices, but it'd still be less good than the older code. Unclear how important this is.
2017-12-03 12:14:36 -06:00
error: aborting due to 2 previous errors
update tests
2018-03-03 08:59:40 -06:00
For more information about this error, try `rustc --explain E0309`.
Reference in New Issue Copy Permalink