Skip to content

regression: cycle detected when computing whether impls specialize one another #125197

Closed

Description

@BoxyUwU
[INFO] [stdout] error[E0391]: cycle detected when computing whether impls specialize one another
[INFO] [stdout]   --> /opt/rustwide/workdir/src/lib.rs:54:1
[INFO] [stdout]    |
[INFO] [stdout] 54 | impl<T: Identifier> PartialEq<T> for AnyId {
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |

Activity

  1. added
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    on May 17, 2024
  2. added
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
    on May 17, 2024
  3. added this to the 1.79.0 milestone on May 17, 2024
  4. compiler-errors commented on May 17, 2024

    @compiler-errors
    Contributor

    Bisecting this...

  5. compiler-errors commented on May 17, 2024

    @compiler-errors
    Contributor

    This bisected in #122791. This crate is using specialization, which we don't stably support.

    This has some interactions with specialization, and so breaks a few UI tests that I don't agree should've ever worked in the first place, and also breaks a handful of crates in a way that I don't believe is a problem.

  6. added
    P-lowLow priority
    and removed
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    on May 17, 2024
  7. added and removed
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
    on May 17, 2024
  8. Mark-Simulacrum commented on Jun 7, 2024

    @Mark-Simulacrum
    Member

    @compiler-errors How is that not feature gated? I don't see feature gates in the repos above and presumably it built on stable in order to regress here?

  9. compiler-errors commented on Jun 7, 2024

    @compiler-errors
    Contributor

    I am mistaken then, @Mark-Simulacrum. I thought I looked at these crates, but perhaps I was looking at the wrong one.

  10. compiler-errors commented on Jun 7, 2024

    @compiler-errors
    Contributor

    I'll look back into this...

  11. compiler-errors commented on Jun 7, 2024

    @compiler-errors
    Contributor

    Opened a PR for this and nominated for beta.

  12. added a commit that references this issue on Jun 7, 2024
  13. added
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    and removed
    P-lowLow priority
    on Jun 7, 2024
  14. added a commit that references this issue on Jun 11, 2024
  15. removed
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    on Jun 11, 2024
  16. apiraino commented on Aug 5, 2024

    @apiraino
    Contributor

    #126772 was merged, so can this be closed as fixed? cc @BoxyUwU

  17. compiler-errors commented on Aug 5, 2024

    @compiler-errors
    Contributor

    ya this was fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

A-specializationArea: Trait impl specializationF-specialization`#![feature(specialization)]`T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions