mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e30d27be00
rust/tests/ui/specialization/issue-38091.stderr

31 lines
1.1 KiB
Plaintext
Raw Normal View History

bless all
2020-06-16 03:06:35 -05:00
warning: the feature `specialization` is incomplete and may not be safe to use and/or cause compiler crashes
Move bounds on associated types to the type Given `trait X { type U; }` the bound `<Self as X>::U` now lives on the type, rather than the trait. This is feature gated on `feature(generic_associated_types)` for now until more testing can be done. The also enabled type-generic associated types since we no longer need "implies bounds".
2020-06-11 10:50:34 -05:00
--> $DIR/issue-38091.rs:1:12
bless all
2020-06-16 03:06:35 -05:00
|
LL | #![feature(specialization)]
| ^^^^^^^^^^^^^^
|
= note: see issue #31844 <https://github.com/rust-lang/rust/issues/31844> for more information
Suggest minimal subset features in `incomplete_features` lint
2020-10-13 18:35:32 -05:00
= help: consider using `min_specialization` instead, which is more stable and complete
bless ui tests
2022-09-18 10:55:36 -05:00
= note: `#[warn(incomplete_features)]` on by default
bless all
2020-06-16 03:06:35 -05:00
Check associated type satisfy their bounds This was currently only happening due to eager normalization, which isn't possible if there's specialization or bound variables.
2020-05-30 11:21:25 -05:00
error[E0277]: the trait bound `(): Valid` is not satisfied
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
--> $DIR/issue-38091.rs:12:23
Check associated type satisfy their bounds This was currently only happening due to eager normalization, which isn't possible if there's specialization or bound variables.
2020-05-30 11:21:25 -05:00
|
LL | default type Ty = ();
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
| ^^ the trait `Valid` is not implemented for `()`
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
|
Point out if a local trait has no implementations
2023-09-09 22:33:07 -05:00
help: this trait has no implementations, consider adding one
--> $DIR/issue-38091.rs:20:1
|
LL | trait Valid {}
| ^^^^^^^^^^^
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
note: required by a bound in `Iterate::Ty`
--> $DIR/issue-38091.rs:5:14
|
LL | type Ty: Valid;
| ^^^^^ required by this bound in `Iterate::Ty`
Check associated type satisfy their bounds This was currently only happening due to eager normalization, which isn't possible if there's specialization or bound variables.
2020-05-30 11:21:25 -05:00
Avoid cycles from projection bounds Only check the own predicates of associated types when confirming projection candidates. Also consider implied bounds when comparing trait and impl methods.
2020-07-25 07:41:53 -05:00
error: aborting due to previous error; 1 warning emitted
bless all
2020-06-16 03:06:35 -05:00
Avoid cycles from projection bounds Only check the own predicates of associated types when confirming projection candidates. Also consider implied bounds when comparing trait and impl methods.
2020-07-25 07:41:53 -05:00
For more information about this error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink