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

31 lines
988 B
Plaintext
Raw Normal View History

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
warning: not reporting region error due to -Znll
handle projections with regions
2017-12-05 12:15:23 -06:00
--> $DIR/projection-no-regions-fn.rs:24: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
|
24 | Box::new(x.next())
| ^^^^^^^^^^^^^^^^^^
warning: not reporting region error due to -Znll
handle projections with regions
2017-12-05 12:15:23 -06:00
--> $DIR/projection-no-regions-fn.rs:40: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
|
40 | Box::new(x.next())
| ^^^^^^^^^^^^^^^^^^
use `report_generic_bound_failure` when we can in the compiler
2017-12-19 10:12:56 -06:00
error[E0309]: the associated type `<T as std::iter::Iterator>::Item` may not live long enough
handle projections with regions
2017-12-05 12:15:23 -06:00
--> $DIR/projection-no-regions-fn.rs:24: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
|
24 | Box::new(x.next())
| ^^^^^^^^^^^^^^^^^^
use `report_generic_bound_failure` when we can in the compiler
2017-12-19 10:12:56 -06:00
|
= help: consider adding an explicit lifetime bound `<T as std::iter::Iterator>::Item: ReEarlyBound(0, '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
use `report_generic_bound_failure` when we can in the compiler
2017-12-19 10:12:56 -06:00
error[E0309]: the associated type `<T as std::iter::Iterator>::Item` may not live long enough
handle projections with regions
2017-12-05 12:15:23 -06:00
--> $DIR/projection-no-regions-fn.rs:40: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
|
40 | Box::new(x.next())
| ^^^^^^^^^^^^^^^^^^
use `report_generic_bound_failure` when we can in the compiler
2017-12-19 10:12:56 -06:00
|
= help: consider adding an explicit lifetime bound `<T as std::iter::Iterator>::Item: ReEarlyBound(0, '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
Reference in New Issue Copy Permalink