rust/tests/ui/lifetimes/unnamed-closure-doesnt-life-long-enough-issue-67634.stderr

error[E0373]: closure may outlive the current function, but it borrows `a`, which is owned by the current function
  --> $DIR/unnamed-closure-doesnt-life-long-enough-issue-67634.rs:2:44
   |
LL |     [0].iter().flat_map(|a| [0].iter().map(|_| &a));
   |                                            ^^^  - `a` is borrowed here
   |                                            |
   |                                            may outlive borrowed value `a`
   |
note: closure is returned here
  --> $DIR/unnamed-closure-doesnt-life-long-enough-issue-67634.rs:2:29
   |
LL |     [0].iter().flat_map(|a| [0].iter().map(|_| &a));
   |                             ^^^^^^^^^^^^^^^^^^^^^^
help: to force the closure to take ownership of `a` (and any other referenced variables), use the `move` keyword
   |
LL |     [0].iter().flat_map(|a| [0].iter().map(move |_| &a));
   |                                            ++++

error: aborting due to previous error

For more information about this error, try `rustc --explain E0373`.
Use an 'approximate' universal upper bound when reporting region errors Fixes #67765 When reporting errors during MIR region inference, we sometimes use `universal_upper_bound` to obtain a named universal region that we can display to the user. However, this is not always possible - in a case like `fn foo<'a, 'b>() { .. }`, the only upper bound for a region containing `'a` and `'b` is `'static`. When displaying diagnostics, it's usually better to display some named region (even if there are multiple involved) rather than fall back to a generic error involving `'static`. This commit adds a new `approx_universal_upper_bound` method, which uses the lowest-numbered universal region if the only alternative is to return `'static`. 2020-06-27 12:54:56 -05:00			error[E0373]: closure may outlive the current function, but it borrows `a`, which is owned by the current function
			`--> $DIR/unnamed-closure-doesnt-life-long-enough-issue-67634.rs:2:44`
Do not ICE on lifetime error involving closures 2019-12-28 15:51:29 -06:00			`\|`
			`LL \| [0].iter().flat_map(\|a\| [0].iter().map(\|_\| &a));`
Use an 'approximate' universal upper bound when reporting region errors Fixes #67765 When reporting errors during MIR region inference, we sometimes use `universal_upper_bound` to obtain a named universal region that we can display to the user. However, this is not always possible - in a case like `fn foo<'a, 'b>() { .. }`, the only upper bound for a region containing `'a` and `'b` is `'static`. When displaying diagnostics, it's usually better to display some named region (even if there are multiple involved) rather than fall back to a generic error involving `'static`. This commit adds a new `approx_universal_upper_bound` method, which uses the lowest-numbered universal region if the only alternative is to return `'static`. 2020-06-27 12:54:56 -05:00			\| ^^^ - `a` is borrowed here
			`\| \|`
			\| may outlive borrowed value `a`
Do not ICE on lifetime error involving closures 2019-12-28 15:51:29 -06:00			`\|`
Use an 'approximate' universal upper bound when reporting region errors Fixes #67765 When reporting errors during MIR region inference, we sometimes use `universal_upper_bound` to obtain a named universal region that we can display to the user. However, this is not always possible - in a case like `fn foo<'a, 'b>() { .. }`, the only upper bound for a region containing `'a` and `'b` is `'static`. When displaying diagnostics, it's usually better to display some named region (even if there are multiple involved) rather than fall back to a generic error involving `'static`. This commit adds a new `approx_universal_upper_bound` method, which uses the lowest-numbered universal region if the only alternative is to return `'static`. 2020-06-27 12:54:56 -05:00			`note: closure is returned here`
			`--> $DIR/unnamed-closure-doesnt-life-long-enough-issue-67634.rs:2:29`
			`\|`
			`LL \| [0].iter().flat_map(\|a\| [0].iter().map(\|_\| &a));`
			`\| ^^^^^^^^^^^^^^^^^^^^^^`
			help: to force the closure to take ownership of `a` (and any other referenced variables), use the `move` keyword
			`\|`
			`LL \| [0].iter().flat_map(\|a\| [0].iter().map(move \|_\| &a));`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ++++`
Do not ICE on lifetime error involving closures 2019-12-28 15:51:29 -06:00
			`error: aborting due to previous error`

Use an 'approximate' universal upper bound when reporting region errors Fixes #67765 When reporting errors during MIR region inference, we sometimes use `universal_upper_bound` to obtain a named universal region that we can display to the user. However, this is not always possible - in a case like `fn foo<'a, 'b>() { .. }`, the only upper bound for a region containing `'a` and `'b` is `'static`. When displaying diagnostics, it's usually better to display some named region (even if there are multiple involved) rather than fall back to a generic error involving `'static`. This commit adds a new `approx_universal_upper_bound` method, which uses the lowest-numbered universal region if the only alternative is to return `'static`. 2020-06-27 12:54:56 -05:00			For more information about this error, try `rustc --explain E0373`.