rust/tests/ui/fmt/ifmt-unimpl.stderr

error[E0277]: the trait bound `str: UpperHex` is not satisfied
  --> $DIR/ifmt-unimpl.rs:2:21
   |
LL |     format!("{:X}", "3");
   |              ----   ^^^ the trait `UpperHex` is not implemented for `str`
   |              |
   |              required by this formatting parameter
   |
   = help: the following other types implement trait `UpperHex`:
             &T
             &mut T
             NonZero<T>
             Saturating<T>
             Wrapping<T>
             i128
             i16
             i32
           and 9 others
   = note: required for `&str` to implement `UpperHex`
   = note: this error originates in the macro `$crate::__export::format_args` which comes from the expansion of the macro `format` (in Nightly builds, run with -Z macro-backtrace for more info)

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 10:40:56 +03:00			error[E0277]: the trait bound `str: UpperHex` is not satisfied
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/ifmt-unimpl.rs:2:21`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\|`
			`LL \| format!("{:X}", "3");`
Remove detail from label/note that is already available in other note Remove the "which is required by `{root_obligation}`" post-script in "the trait `X` is not implemented for `Y`" explanation in E0277. This information is already conveyed in the notes explaining requirements, making it redundant while making the text (particularly in labels) harder to read. ``` error[E0277]: the trait bound `NotCopy: Copy` is not satisfied --> $DIR/wf-static-type.rs:10:13 \| LL \| static FOO: IsCopy<Option<NotCopy>> = IsCopy { t: None }; \| ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `NotCopy` \| = note: required for `Option<NotCopy>` to implement `Copy` note: required by a bound in `IsCopy` --> $DIR/wf-static-type.rs:7:17 \| LL \| struct IsCopy<T:Copy> { t: T } \| ^^^^ required by this bound in `IsCopy` ``` vs the prior ``` error[E0277]: the trait bound `NotCopy: Copy` is not satisfied --> $DIR/wf-static-type.rs:10:13 \| LL \| static FOO: IsCopy<Option<NotCopy>> = IsCopy { t: None }; \| ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `NotCopy`, which is required by `Option<NotCopy>: Copy` \| = note: required for `Option<NotCopy>` to implement `Copy` note: required by a bound in `IsCopy` --> $DIR/wf-static-type.rs:7:17 \| LL \| struct IsCopy<T:Copy> { t: T } \| ^^^^ required by this bound in `IsCopy` ``` 2024-10-24 21:14:17 +00:00			\| ---- ^^^ the trait `UpperHex` is not implemented for `str`
Bless UI tests. 2023-03-27 14:43:17 +02:00			`\| \|`
Implement DesugaringKind::FormatLiteral 2025-06-16 17:51:29 +02:00			`\| required by this formatting parameter`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\|`
Mention implementers of unsatisfied trait When encountering an unsatisfied trait bound, if there are no other suggestions, mention all the types that do implement that trait: ``` error[E0277]: the trait bound `f32: Foo` is not satisfied --> $DIR/impl_wf.rs:22:6 \| LL \| impl Baz<f32> for f32 { } \| ^^^^^^^^ the trait `Foo` is not implemented for `f32` \| = help: the following other types implement trait `Foo`: Option<T> i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 \| LL \| trait Baz<U: ?Sized> where U: Foo { } \| ^^^ required by this bound in `Baz` ``` Mention implementers of traits in `ImplObligation`s. Do not mention other `impl`s for closures, ranges and `?`. 2021-12-13 20:56:40 +00:00			= help: the following other types implement trait `UpperHex`:
Use `TraitRef::to_string` sorting in favor of `TraitRef::ord`, as the latter compares `DefId`s which we need to avoid 2024-03-21 12:55:28 +00:00			`&T`
			`&mut T`
			`NonZero<T>`
			`Saturating<T>`
			`Wrapping<T>`
			`i128`
Don't sort strings right after we just sorted by types 2023-06-27 23:31:06 +00:00			`i16`
			`i32`
Implement `NonZero` traits generically. 2024-02-17 01:45:15 +01:00			`and 9 others`
Reword "Required because of the requirements on the impl of ..." 2022-08-15 21:31:37 +01:00			= note: required for `&str` to implement `UpperHex`
Update tests. 2023-04-20 20:18:22 +02:00			= note: this error originates in the macro `$crate::__export::format_args` which comes from the expansion of the macro `format` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02: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`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			For more information about this error, try `rustc --explain E0277`.