rust/tests/ui/traits/bound/on-structs-and-enums-xc1.stderr

error[E0277]: the trait bound `f64: Trait` is not satisfied
  --> $DIR/on-structs-and-enums-xc1.rs:12:14
   |
LL |     let bar: Bar<f64> = return;
   |              ^^^^^^^^ the trait `Trait` is not implemented for `f64`
   |
note: required by a bound in `Bar`
  --> $DIR/auxiliary/on_structs_and_enums_xc.rs:9:16
   |
LL | pub enum Bar<T:Trait> {
   |                ^^^^^ required by this bound in `Bar`

error[E0277]: the trait bound `{integer}: Trait` is not satisfied
  --> $DIR/on-structs-and-enums-xc1.rs:9:12
   |
LL |         x: 3
   |            ^ the trait `Trait` is not implemented for `{integer}`
   |
note: required by a bound in `Foo`
  --> $DIR/auxiliary/on_structs_and_enums_xc.rs:5:18
   |
LL | pub struct Foo<T:Trait> {
   |                  ^^^^^ required by this bound in `Foo`

error: aborting due to 2 previous errors

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 `f64: Trait` is not satisfied
Organize trait test files 2021-02-08 16:15:45 -06:00			`--> $DIR/on-structs-and-enums-xc1.rs:12:14`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
			`LL \| let bar: Bar<f64> = return;`
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			\| ^^^^^^^^ the trait `Trait` is not implemented for `f64`
Remove trailing whitespace from error messages 2021-06-10 06:52:00 -05:00			`\|`
Use note to point at bound introducing requirement 2021-07-31 11:26:55 -05:00			note: required by a bound in `Bar`
			`--> $DIR/auxiliary/on_structs_and_enums_xc.rs:9:16`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Use `PredicateObligation`s instead of `Predicate`s Keep more information about trait binding failures. 2020-03-03 17:07:04 -06:00			`LL \| pub enum Bar<T:Trait> {`
Use note to point at bound introducing requirement 2021-07-31 11:26:55 -05:00			\| ^^^^^ required by this bound in `Bar`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -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			error[E0277]: the trait bound `{integer}: Trait` is not satisfied
Adjust messages, address some nits 2022-08-18 07:16:35 -05:00			`--> $DIR/on-structs-and-enums-xc1.rs:9:12`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Point at struct field if possible 2022-08-16 23:57:17 -05:00			`LL \| x: 3`
Adjust messages, address some nits 2022-08-18 07:16:35 -05:00			\| ^ the trait `Trait` is not implemented for `{integer}`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Point at source of trait bound obligations in more places Be more thorough in using `ItemObligation` and `BindingObligation` when evaluating obligations so that we can point at trait bounds that introduced unfulfilled obligations. We no longer incorrectly point at unrelated trait bounds (`substs-ppaux.verbose.stderr`). In particular, we now point at trait bounds on method calls. We no longer point at "obvious" obligation sources (we no longer have a note pointing at `Trait` saying "required by a bound in `Trait`", like in `associated-types-no-suitable-supertrait*`). Address part of #89418. 2021-10-05 18:04:09 -05:00			note: required by a bound in `Foo`
			`--> $DIR/auxiliary/on_structs_and_enums_xc.rs:5:18`
Various diagnostics clean ups/tweaks * Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition 2021-07-17 13:13:50 -05:00			`\|`
			`LL \| pub struct Foo<T:Trait> {`
Point at source of trait bound obligations in more places Be more thorough in using `ItemObligation` and `BindingObligation` when evaluating obligations so that we can point at trait bounds that introduced unfulfilled obligations. We no longer incorrectly point at unrelated trait bounds (`substs-ppaux.verbose.stderr`). In particular, we now point at trait bounds on method calls. We no longer point at "obvious" obligation sources (we no longer have a note pointing at `Trait` saying "required by a bound in `Trait`", like in `associated-types-no-suitable-supertrait*`). Address part of #89418. 2021-10-05 18:04:09 -05:00			\| ^^^^^ required by this bound in `Foo`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to 2 previous errors`

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