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 a bound introduced by this call
   |
   = help: the following other types implement trait `UpperHex`:
             isize
             i8
             i16
             i32
             i64
             i128
             usize
             u8
           and 20 others
   = note: required for `&str` to implement `UpperHex`
note: required by a bound in `core::fmt::rt::Argument::<'a>::new_upper_hex`
  --> $SRC_DIR/core/src/fmt/rt.rs:LL:COL
   = 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 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 02:40:56 -05:00			error[E0277]: the trait bound `str: UpperHex` is not satisfied
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/ifmt-unimpl.rs:2:21`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
			`LL \| format!("{:X}", "3");`
Bless UI tests. 2023-03-27 07:43:17 -05:00			\| ---- ^^^ the trait `UpperHex` is not implemented for `str`
			`\| \|`
			`\| required by a bound introduced by this call`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05: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 14:56:40 -06:00			= help: the following other types implement trait `UpperHex`:
Don't sort strings right after we just sorted by types 2023-06-27 18:31:06 -05:00			`isize`
			`i8`
			`i16`
			`i32`
			`i64`
			`i128`
			`usize`
			`u8`
Bless tests for portable-simd sync API changes resulted in subtle MIR and impl differences 2023-05-10 20:28:26 -05:00			`and 20 others`
Reword "Required because of the requirements on the impl of ..." 2022-08-15 15:31:37 -05:00			= note: required for `&str` to implement `UpperHex`
Update tests. 2023-04-20 13:18:22 -05:00			note: required by a bound in `core::fmt::rt::Argument::<'a>::new_upper_hex`
			`--> $SRC_DIR/core/src/fmt/rt.rs:LL:COL`
			= 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 07:28:26 -05:00
			`error: aborting due to previous error`

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