rust/tests/ui/nll/closure-requirements/propagate-from-trait-match.stderr

note: external requirements
  --> $DIR/propagate-from-trait-match.rs:32:36
   |
LL |     establish_relationships(value, |value| {
   |                                    ^^^^^^^
   |
   = note: defining type: supply::<'?1, T>::{closure#0} with closure args [
               i32,
               extern "rust-call" fn((T,)),
               (),
           ]
   = note: number of external vids: 2
   = note: where T: '?1

note: no external requirements
  --> $DIR/propagate-from-trait-match.rs:28:1
   |
LL | / fn supply<'a, T>(value: T)
LL | | where
LL | |     T: Trait<'a>,
   | |_________________^
   |
   = note: defining type: supply::<'?1, T>

error[E0309]: the parameter type `T` may not live long enough
  --> $DIR/propagate-from-trait-match.rs:43:9
   |
LL |         require(value);
   |         ^^^^^^^^^^^^^^ ...so that the type `T` will meet its required lifetime bounds
   |
help: consider adding an explicit lifetime bound...
   |
LL |     T: Trait<'a> + 'a,
   |                  ++++

error: aborting due to previous error

For more information about this error, try `rustc --explain E0309`.
Diagnostics should start lowercase 2020-01-10 08:13:05 -06:00			`note: external requirements`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/propagate-from-trait-match.rs:32:36`
add a test regarding relating closure and fn generics Turns out this works but we had no test targeting it. 2017-12-06 03:56:03 -06:00			`\|`
Use def_span for external requirements. 2022-08-31 13:17:32 -05:00			`LL \| establish_relationships(value, \|value\| {`
			`\| ^^^^^^^`
add a test regarding relating closure and fn generics Turns out this works but we had no test targeting it. 2017-12-06 03:56:03 -06:00			`\|`
refactor(rustc_middle): Substs -> GenericArg 2023-07-11 16:35:29 -05:00			`= note: defining type: supply::<'?1, T>::{closure#0} with closure args [`
add a test regarding relating closure and fn generics Turns out this works but we had no test targeting it. 2017-12-06 03:56:03 -06:00			`i32,`
Include trailing comma in multiline Debug representation This commit changes the behavior of Formatter::debug_struct, debug_tuple, debug_list, debug_set, and debug_map to render trailing commas in {:#?} mode, which is the dominant style in modern Rust code. Before: Language { name: "Rust", trailing_commas: false } After: Language { name: "Rust", trailing_commas: true, } 2019-04-03 09:30:08 -05:00			`extern "rust-call" fn((T,)),`
rustc: keep upvars tupled in {Closure,Generator}Substs. 2020-03-12 20:23:38 -05:00			`(),`
add a test regarding relating closure and fn generics Turns out this works but we had no test targeting it. 2017-12-06 03:56:03 -06:00			`]`
Fix tests 2018-09-06 21:57:05 -05:00			`= note: number of external vids: 2`
vars are ? 2023-04-21 19:08:38 -05:00			`= note: where T: '?1`
add a test regarding relating closure and fn generics Turns out this works but we had no test targeting it. 2017-12-06 03:56:03 -06:00
Diagnostics should start lowercase 2020-01-10 08:13:05 -06:00			`note: no external requirements`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/propagate-from-trait-match.rs:28:1`
add a test regarding relating closure and fn generics Turns out this works but we had no test targeting it. 2017-12-06 03:56:03 -06:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| / fn supply<'a, T>(value: T)`
			`LL \| \| where`
			`LL \| \| T: Trait<'a>,`
Use def_span for external requirements. 2022-08-31 13:17:32 -05:00			`\| \|_________________^`
add a test regarding relating closure and fn generics Turns out this works but we had no test targeting it. 2017-12-06 03:56:03 -06:00			`\|`
vars are ? 2023-04-21 19:08:38 -05:00			`= note: defining type: supply::<'?1, T>`
add a test regarding relating closure and fn generics Turns out this works but we had no test targeting it. 2017-12-06 03:56:03 -06:00
Blindly update the `#[rustc_region]` tests which got touched by the NLL diagnostic change. 2018-07-31 07:35:43 -05:00			error[E0309]: the parameter type `T` may not live long enough
use spans in TypeTest rather than mir::Location Spans are independent of the body being borrow-checked, so they don't need remapping when promoting type-tests and they yield more specific error spans inside bodies of closures/inline consts. 2022-10-03 05:45:02 -05:00			`--> $DIR/propagate-from-trait-match.rs:43:9`
Blindly update the `#[rustc_region]` tests which got touched by the NLL diagnostic change. 2018-07-31 07:35:43 -05:00			`\|`
use spans in TypeTest rather than mir::Location Spans are independent of the body being borrow-checked, so they don't need remapping when promoting type-tests and they yield more specific error spans inside bodies of closures/inline consts. 2022-10-03 05:45:02 -05:00			`LL \| require(value);`
			\| ^^^^^^^^^^^^^^ ...so that the type `T` will meet its required lifetime bounds
Bless tests. 2022-03-14 09:56:37 -05:00			`\|`
			`help: consider adding an explicit lifetime bound...`
			`\|`
			`LL \| T: Trait<'a> + 'a,`
			`\| ++++`
Blindly update the `#[rustc_region]` tests which got touched by the NLL diagnostic change. 2018-07-31 07:35:43 -05:00
add a test regarding relating closure and fn generics Turns out this works but we had no test targeting it. 2017-12-06 03:56:03 -06:00			`error: aborting due to previous error`

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