rust/src/test/ui/hrtb/hrtb-cache-issue-54302.stderr

error: implementation of `Deserialize` is not general enough
  --> $DIR/hrtb-cache-issue-54302.rs:19:5
   |
LL |     assert_deserialize_owned::<&'static str>(); //~ ERROR
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: `&'static str` must implement `Deserialize<'0>`, for any lifetime `'0`
   = note: but `&str` actually implements `Deserialize<'1>`, for some lifetime `'1`

error: aborting due to previous error
apply the new placeholder errors even with just one placeholder 2018-11-18 12:25:53 -06:00			error: implementation of `Deserialize` is not general enough
make evaluation track whether outlives relationships mattered Previously, evaluation ignored outlives relationships. Since we using evaluation to skip the "normal" trait selection (which enforces outlives relationships) this led to incorrect results in some cases. 2018-09-20 12:56:11 -05:00			`--> $DIR/hrtb-cache-issue-54302.rs:19:5`
			`\|`
			`LL \| assert_deserialize_owned::<&'static str>(); //~ ERROR`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
			`\|`
When mentioning lifetimes, put either the trait ref or the self type closer to the lifetimes When mentioning lifetimes, only invert wording between the expected trait and the self type when the self type has the vid. This way, the lifetimes always stay close to the self type or trait ref that actually contains them. 2019-01-26 13:25:36 -06:00			= note: `&'static str` must implement `Deserialize<'0>`, for any lifetime `'0`
			= note: but `&str` actually implements `Deserialize<'1>`, for some lifetime `'1`
make evaluation track whether outlives relationships mattered Previously, evaluation ignored outlives relationships. Since we using evaluation to skip the "normal" trait selection (which enforces outlives relationships) this led to incorrect results in some cases. 2018-09-20 12:56:11 -05:00
			`error: aborting due to previous error`