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

error[E0277]: the size for values of type `(dyn Fn() + 'static)` cannot be known at compilation time
  --> $DIR/issue-23281.rs:4:27
   |
LL |     pub fn function(funs: Vec<dyn Fn() -> ()>) {}
   |                           ^^^^^^^^^^^^^^^^^^^ doesn't have a size known at compile-time
   |
   = help: the trait `Sized` is not implemented for `(dyn Fn() + 'static)`
note: required by an implicit `Sized` bound in `Vec`
  --> $DIR/issue-23281.rs:8:12
   |
LL | struct Vec<T> {
   |            ^ required by the implicit `Sized` requirement on this type parameter in `Vec`
help: you could relax the implicit `Sized` bound on `T` if it were used through indirection like `&T` or `Box<T>`
  --> $DIR/issue-23281.rs:8:12
   |
LL | struct Vec<T> {
   |            ^ this could be changed to `T: ?Sized`...
LL |     t: T,
   |        - ...if indirection were used here: `Box<T>`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 07:40:56 +00:00			error[E0277]: the size for values of type `(dyn Fn() + 'static)` cannot be known at compilation time
Point at arguments or output when fn obligations come from them, or ident when they don't 2020-01-18 22:57:56 +00:00			`--> $DIR/issue-23281.rs:4:27`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
Update ui test suite to use dyn 2019-05-28 18:46:13 +00:00			`LL \| pub fn function(funs: Vec<dyn Fn() -> ()>) {}`
Point at arguments or output when fn obligations come from them, or ident when they don't 2020-01-18 22:57:56 +00:00			`\| ^^^^^^^^^^^^^^^^^^^ doesn't have a size known at compile-time`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 07:40:56 +00:00			= help: the trait `Sized` is not implemented for `(dyn Fn() + 'static)`
On E0277 be clearer about implicit `Sized` bounds on type params and assoc types ``` error[E0277]: the size for values of type `[i32]` cannot be known at compilation time --> f100.rs:2:33 \| 2 \| let _ = std::mem::size_of::<[i32]>(); \| ^^^^^ doesn't have a size known at compile-time \| = help: the trait `Sized` is not implemented for `[i32]` note: required by an implicit `Sized` bound in `std::mem::size_of` --> /home/gh-estebank/rust/library/core/src/mem/mod.rs:312:22 \| 312 \| pub const fn size_of<T>() -> usize { \| ^ required by the implicit `Sized` requirement on this bound in `size_of` ``` Fix #120178. 2024-01-24 21:29:15 +00:00			note: required by an implicit `Sized` bound in `Vec`
Use note to point at bound introducing requirement 2021-07-31 16:26:55 +00:00			`--> $DIR/issue-23281.rs:8:12`
			`\|`
			`LL \| struct Vec<T> {`
review comment: change wording 2024-01-30 19:47:45 +00:00			\| ^ required by the implicit `Sized` requirement on this type parameter in `Vec`
Provide `help` when `T: ?Sized` can't be suggested 2020-06-17 00:24:16 +00:00			help: you could relax the implicit `Sized` bound on `T` if it were used through indirection like `&T` or `Box<T>`
			`--> $DIR/issue-23281.rs:8:12`
			`\|`
			`LL \| struct Vec<T> {`
			\| ^ this could be changed to `T: ?Sized`...
			`LL \| t: T,`
Miscellaneous small diagnostics cleanup 2021-02-04 05:41:18 +00:00			\| - ...if indirection were used here: `Box<T>`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00: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 21:11:54 +00:00
			For more information about this error, try `rustc --explain E0277`.