rust/tests/ui/associated-consts/associated-const-generic-obligations.stderr

error[E0326]: implemented const `FROM` has an incompatible type for trait
  --> $DIR/associated-const-generic-obligations.rs:14:17
   |
LL |     const FROM: &'static str = "foo";
   |                 ^^^^^^^^^^^^ expected associated type, found `&'static str`
   |
note: type in trait
  --> $DIR/associated-const-generic-obligations.rs:10:17
   |
LL |     const FROM: Self::Out;
   |                 ^^^^^^^^^
   = note: expected associated type `<T as Foo>::Out`
                    found reference `&'static str`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0326`.
Fix #54822 and associated faulty tests Type checking associated constants can require trait bounds, but an empty parameter environment was provided to the trait solver. Providing an appropriate parameter environment seems to fix #54822 and also make one of the cases in src/test/ui/nll/trait-associated-constant.rs that should compile successfully do so. It also (slightly) improves the error message in src/test/ui/associated-const/associated-const-generic-obligations.rs 2019-03-10 21:18:38 -05:00			error[E0326]: implemented const `FROM` has an incompatible type for trait
			`--> $DIR/associated-const-generic-obligations.rs:14:17`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
			`LL \| const FROM: &'static str = "foo";`
Modify primary span label for E0308 The previous output was unintuitive to users. 2023-01-02 20:00:33 -06:00			\| ^^^^^^^^^^^^ expected associated type, found `&'static str`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Tweak assoc type obligation spans * Point at RHS of associated type in obligation span * Point at `impl` assoc type on projection error * Reduce verbosity of recursive obligations * Point at source of binding lifetime obligation * Tweak "required bound" note * Tweak "expected... found opaque (return) type" labels * Point at set type in impl assoc type WF errors 2021-12-10 20:20:41 -06:00			`note: type in trait`
			`--> $DIR/associated-const-generic-obligations.rs:10:17`
			`\|`
			`LL \| const FROM: Self::Out;`
			`\| ^^^^^^^^^`
Specific labels when referring to "expected" and "found" types 2019-11-13 16:16:56 -06:00			= note: expected associated type `<T as Foo>::Out`
			found reference `&'static str`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
Fix #54822 and associated faulty tests Type checking associated constants can require trait bounds, but an empty parameter environment was provided to the trait solver. Providing an appropriate parameter environment seems to fix #54822 and also make one of the cases in src/test/ui/nll/trait-associated-constant.rs that should compile successfully do so. It also (slightly) improves the error message in src/test/ui/associated-const/associated-const-generic-obligations.rs 2019-03-10 21:18:38 -05:00			For more information about this error, try `rustc --explain E0326`.