rust/tests/ui/object-lifetime/object-lifetime-default-dyn-binding-nonstatic3.stderr

error[E0228]: the lifetime bound for this object type cannot be deduced from context; please supply an explicit bound
  --> $DIR/object-lifetime-default-dyn-binding-nonstatic3.rs:16:36
   |
LL | fn bar(x: &str) -> &dyn Foo<Item = dyn Bar> { &() }
   |                                    ^^^^^^^

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0228`.
use static as object-lifetime default for type XX in `Foo<Item=XX>` Currently the default is "inherited" from context, so e.g. `&impl Foo<Item = dyn Bar>` would default to `&'x impl Foo<Item = dyn Bar + 'x>`, but this triggers an ICE and is not very consistent. This patch doesn't implement what I expect would be the correct semantics, because those are likely too complex. Instead, it handles what I'd expect to be the common case -- where the trait has no lifetime parameters. 2019-08-12 14:41:05 +00:00			`error[E0228]: the lifetime bound for this object type cannot be deduced from context; please supply an explicit bound`
			`--> $DIR/object-lifetime-default-dyn-binding-nonstatic3.rs:16:36`
			`\|`
			`LL \| fn bar(x: &str) -> &dyn Foo<Item = dyn Bar> { &() }`
			`\| ^^^^^^^`

make `type_flags(ReError) & HAS_ERROR` 2024-03-19 20:58:37 +00:00			`error: aborting due to 1 previous error`
use static as object-lifetime default for type XX in `Foo<Item=XX>` Currently the default is "inherited" from context, so e.g. `&impl Foo<Item = dyn Bar>` would default to `&'x impl Foo<Item = dyn Bar + 'x>`, but this triggers an ICE and is not very consistent. This patch doesn't implement what I expect would be the correct semantics, because those are likely too complex. Instead, it handles what I'd expect to be the common case -- where the trait has no lifetime parameters. 2019-08-12 14:41:05 +00:00
make `type_flags(ReError) & HAS_ERROR` 2024-03-19 20:58:37 +00:00			For more information about this error, try `rustc --explain E0228`.