Skip to content

regression: conflicting implementations of trait Visitable for type Box<_> #127341

Closed

Description

@Mark-Simulacrum

Not entirely clear if this is caused by a new impl in std or trait solver changes.

[INFO] [stdout] error[E0119]: conflicting implementations of trait `Visitable` for type `Box<_>`
[INFO] [stdout]   --> src/std_impls.rs:49:1
[INFO] [stdout]    |
[INFO] [stdout] 25 | / impl<C: 'static> Visitable for C
[INFO] [stdout] 26 | | where
[INFO] [stdout] 27 | |     for<'a> &'a C: IntoIterator,
[INFO] [stdout] 28 | |     for<'a> <&'a C as IntoIterator>::Item: AsVisitable<'a>,
[INFO] [stdout]    | |___________________________________________________________- first implementation here
[INFO] [stdout] ...
[INFO] [stdout] 49 |   impl<T: Visitable> Visitable for Box<T> {
[INFO] [stdout]    |   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for `Box<_>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: downstream crates may implement trait `std_impls::AsVisitable<'a>` for type `<&'a std::boxed::Box<_> as std::iter::IntoIterator>::Item`

Activity

  1. added
    T-libs-api[DEPRECATED; DO NOT USE]
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    on Jul 4, 2024
  2. added this to the 1.80.0 milestone on Jul 4, 2024
  3. 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 Jul 4, 2024
  4. added
    T-typesRelevant to the types team, which will review and decide on the PR/issue.
    and removed
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
    on Jul 4, 2024
  5. compiler-errors commented on Jul 4, 2024

    @compiler-errors
    Contributor

    Bisected derive-visitor example, since that crate has come up a few times. This bisected to #117164 (comment) cc @lcnr @fmease, though that particular crate didn't get mentioned in the stabilization report.

  6. apiraino commented on Jul 5, 2024

    @apiraino
    Contributor

    Labelling also this as P-high for now (Zulip discussion).

    @rustbot label -I-prioritize +P-high

  7. added
    P-highHigh priority
    and removed
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    on Jul 5, 2024
  8. lcnr commented on Jul 5, 2024

    @lcnr
    Contributor

    all of these look like #114061 to me, I consider this to be intended breakage.

  9. apiraino commented on Jul 5, 2024

    @apiraino
    Contributor

    all of these look like #114061 to me, I consider this to be intended breakage.

    ok then I think it makes sense to add relnotes on #117164

    thanks @lcnr :)

  10. apiraino commented on Jul 11, 2024

    @apiraino
    Contributor

    removing regression label to avoid having this popup in my searches for regressions

    @rustbot label -regression-from-stable-to-beta

  11. lcnr commented on Jul 11, 2024

    @lcnr
    Contributor

    I guess we should close this as intended then.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.T-typesRelevant to the types team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions