rust/tests/ui/issues/issue-18107.stderr

error[E0746]: return type cannot have an unboxed trait object
  --> $DIR/issue-18107.rs:4:5
   |
LL |     dyn AbstractRenderer
   |     ^^^^^^^^^^^^^^^^^^^^ doesn't have a size known at compile-time
   |
help: use `impl AbstractRenderer` as the return type if all return paths have the same type but you want to expose only the trait in the signature
   |
LL |     impl AbstractRenderer
   |
help: use a boxed trait object if all return paths implement trait `AbstractRenderer`
   |
LL |     Box<dyn AbstractRenderer>
   |     ++++                    +

error: aborting due to previous error

For more information about this error, try `rustc --explain E0746`.
Suggest `-> impl Trait` and `-> Box<dyn Trait>` on fn that doesn't return During development, a function could have a return type set that is a bare trait object by accident. We already suggest using either a boxed trait object or `impl Trait` if the return paths will allow it. We now do so too when there are no return paths or they all resolve to `!`. We still don't handle cases where the trait object is not the entirety of the return type gracefully. 2020-04-10 10:19:47 -07:00			`error[E0746]: return type cannot have an unboxed trait object`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-18107.rs:4:5`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
Update ui test suite to use dyn 2019-05-28 14:46:13 -04:00			`LL \| dyn AbstractRenderer`
			`\| ^^^^^^^^^^^^^^^^^^^^ doesn't have a size known at compile-time`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
Ensure tail expression will have a `Ty` for E0746 When the return type is `!Sized` we look for all the returned expressions in the body to fetch their types and provide a reasonable suggestion. The tail expression of the body is normally evaluated after checking whether the return type is `Sized`. Changing the order of the evaluation produces undesirable knock down effects, so we detect the specific case that newcomers are likely to encounter ,returning a single bare trait object, and only in that case we evaluate the tail expression's type so that the suggestion will be accurate. 2020-04-11 11:31:54 -07:00			help: use `impl AbstractRenderer` as the return type if all return paths have the same type but you want to expose only the trait in the signature
Suggest `-> impl Trait` and `-> Box<dyn Trait>` on fn that doesn't return During development, a function could have a return type set that is a bare trait object by accident. We already suggest using either a boxed trait object or `impl Trait` if the return paths will allow it. We now do so too when there are no return paths or they all resolve to `!`. We still don't handle cases where the trait object is not the entirety of the return type gracefully. 2020-04-10 10:19:47 -07:00			`\|`
			`LL \| impl AbstractRenderer`
			`\|`
Ensure tail expression will have a `Ty` for E0746 When the return type is `!Sized` we look for all the returned expressions in the body to fetch their types and provide a reasonable suggestion. The tail expression of the body is normally evaluated after checking whether the return type is `Sized`. Changing the order of the evaluation produces undesirable knock down effects, so we detect the specific case that newcomers are likely to encounter ,returning a single bare trait object, and only in that case we evaluate the tail expression's type so that the suggestion will be accurate. 2020-04-11 11:31:54 -07:00			help: use a boxed trait object if all return paths implement trait `AbstractRenderer`
Suggest `-> impl Trait` and `-> Box<dyn Trait>` on fn that doesn't return During development, a function could have a return type set that is a bare trait object by accident. We already suggest using either a boxed trait object or `impl Trait` if the return paths will allow it. We now do so too when there are no return paths or they all resolve to `!`. We still don't handle cases where the trait object is not the entirety of the return type gracefully. 2020-04-10 10:19:47 -07:00			`\|`
			`LL \| Box<dyn AbstractRenderer>`
Fix late-bound ICE in unsized return suggestion 2022-04-02 14:22:35 -07:00			`\| ++++ +`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
			`error: aborting due to previous error`

Suggest `-> impl Trait` and `-> Box<dyn Trait>` on fn that doesn't return During development, a function could have a return type set that is a bare trait object by accident. We already suggest using either a boxed trait object or `impl Trait` if the return paths will allow it. We now do so too when there are no return paths or they all resolve to `!`. We still don't handle cases where the trait object is not the entirety of the return type gracefully. 2020-04-10 10:19:47 -07:00			For more information about this error, try `rustc --explain E0746`.