os-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: consider returning an `impl Trait` instead of a `dyn Trait`
   |
LL |     impl AbstractRenderer
   |     ~~~~
help: alternatively, box the return type, and wrap all of the returned values in `Box::new`
   |
LL ~     Box<dyn AbstractRenderer>
LL |
LL | {
LL |     match 0 {
LL ~         _ => Box::new(unimplemented!())
   |

error: aborting due to 1 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			`\|`
More accurate suggestion for `-> Box<dyn Trait>` or `-> impl Trait` When encountering `-> Trait`, suggest `-> Box<dyn Trait>` (instead of `-> Box<Trait>`. If there's a single returned type within the `fn`, suggest `-> impl Trait`. 2024-07-19 19:39:37 +00:00			help: consider returning an `impl Trait` instead of a `dyn Trait`
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`
Simplify suggestion when returning bare dyn trait 2023-05-18 01:47:55 +00:00			`\| ~~~~`
More accurate suggestion for `-> Box<dyn Trait>` or `-> impl Trait` When encountering `-> Trait`, suggest `-> Box<dyn Trait>` (instead of `-> Box<Trait>`. If there's a single returned type within the `fn`, suggest `-> impl Trait`. 2024-07-19 19:39:37 +00:00			help: alternatively, box the return type, and wrap all of the returned values in `Box::new`
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			`\|`
Simplify suggestion when returning bare dyn trait 2023-05-18 01:47:55 +00:00			`LL ~ Box<dyn AbstractRenderer>`
			`LL \|`
			`LL \| {`
			`LL \| match 0 {`
			`LL ~ _ => Box::new(unimplemented!())`
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			`\|`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
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`.