rust/src/test/ui/unsized/unsized-bare-typaram.stderr

error[E0277]: the size for values of type `T` cannot be known at compilation time
  --> $DIR/unsized-bare-typaram.rs:2:29
   |
LL | fn bar<T: Sized>() { }
   |        - required by this bound in `bar`
LL | fn foo<T: ?Sized>() { bar::<T>() }
   |        -                    ^ doesn't have a size known at compile-time
   |        |
   |        this type parameter needs to be `Sized`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			error[E0277]: the size for values of type `T` cannot be known at compilation time
Point at type param when it's cause of unfulfilled obligation 2019-09-20 13:58:20 -05:00			`--> $DIR/unsized-bare-typaram.rs:2:29`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Use span label instead of note for cause in E0631 2019-08-24 16:44:43 -05:00			`LL \| fn bar<T: Sized>() { }`
Small tweaks to required bound span 2020-04-06 00:15:06 -05:00			\| - required by this bound in `bar`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`LL \| fn foo<T: ?Sized>() { bar::<T>() }`
Account for `?Sized` type parameter bounds 2020-02-02 04:03:54 -06:00			`\| - ^ doesn't have a size known at compile-time`
Use structured suggestion for restricting bounds When a trait bound is not met and restricting a type parameter would make the restriction hold, use a structured suggestion pointing at an appropriate place (type param in param list or `where` clause). Account for opaque parameters where instead of suggesting extending the `where` clause, we suggest appending the new restriction: `fn foo(impl Trait + UnmetTrait)`. 2019-10-07 16:23:56 -05: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 02:40:56 -05:00			\| this type parameter needs to be `Sized`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0277`.