Repository navigation
Make inductive cycles in coherence ambiguous always - #118649
Conversation
b4f46dd to
7a4f862
Compare
|
|
||
| // This impl overlaps with the `derive` unless we reject the nested | ||
| // `Interval<?1>: PartialOrd<Interval<?1>>` candidate which results | ||
| // in a - currently inductive - cycle. |
There was a problem hiding this comment.
wait this comment can stay
There was a problem hiding this comment.
why did you add another set of - here
|
☔ The latest upstream changes (presumably #118655) made this pull request unmergeable. Please resolve the merge conflicts. |
7a4f862 to
edae624
Compare
This comment has been minimized.
This comment has been minimized.
|
☔ The latest upstream changes (presumably #118324) made this pull request unmergeable. Please resolve the merge conflicts. |
|
r=me after FCP The I propose we change this lint to a hard error in version 1.77, which will be nightly starting from the 2023.12.22 and be stabilized on the 2024.03.21. This is a step towards coinductive traits and matches the existing behavior of @rfcbot fcp merge |
Logical conclusion of #114040
One step after #116493
cc rust-lang/trait-system-refactor-initiative#20
r? lcnr to kick off the FCP after review... maybe we should wait until 1.75 is landed? In that case, I'd still like to get the FCP boxes checked sooner since that'll be near the holidays which means everyone's away.