rust/src/test/ui/nll/ty-outlives/projection-no-regions-fn.stderr

error[E0309]: the associated type `<T as std::iter::Iterator>::Item` may not live long enough
  --> $DIR/projection-no-regions-fn.rs:23:5
   |
LL |     Box::new(x.next())
   |     ^^^^^^^^^^^^^^^^^^
   |
   = help: consider adding an explicit lifetime bound `<T as std::iter::Iterator>::Item: ReEarlyBound(0, 'a)`...

error[E0309]: the associated type `<T as std::iter::Iterator>::Item` may not live long enough
  --> $DIR/projection-no-regions-fn.rs:38:5
   |
LL |     Box::new(x.next())
   |     ^^^^^^^^^^^^^^^^^^
   |
   = help: consider adding an explicit lifetime bound `<T as std::iter::Iterator>::Item: ReEarlyBound(0, 'a)`...

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0309`.
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
updated stderr files and removed feature-gate test for dyn_trait 2018-04-13 19:21:23 -05:00			`--> $DIR/projection-no-regions-fn.rs:23: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			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| Box::new(x.next())`
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			`\|`
			= 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
Update tests 2018-08-31 12:27:11 -05:00			`--> $DIR/projection-no-regions-fn.rs:38: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			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| Box::new(x.next())`
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			`\|`
			= 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`

update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0309`.