Skip to content

regression: abs_diff conflict leading to compilation failures #90320

Closed

Description

@Mark-Simulacrum

The abs_diff API was added to integer types in #88780, which is leading to compilation failures in:

Since it's just a couple cases I suspect we can just accept this regression, but wanted to surface it to T-libs-api. (Maybe a rename or something is in order).

Activity

  1. added this to the 1.57.0 milestone on Oct 26, 2021
  2. added
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    on Oct 26, 2021
  3. nbdd0121 commented on Oct 26, 2021

    @nbdd0121
    Member

    Similar things have caused breakage a few times. I'll investigate.

    @rustbot claim

  4. nbdd0121 commented on Oct 26, 2021

    @nbdd0121
    Member

    Okay, found the issue. The issue is that we try "by_value" before "autoref", and then within each we try "stable" before "unstable", so "unstable by_value" takes priority over "stable autoref". The fix should simply be try all stable candidates first and then try unstable ones. Working on a fix now.

  5. m-ou-se commented on Oct 27, 2021

    @m-ou-se
    Member

    Discussed in the meeting. This is expected and acceptable. Improvements to name resolution to avoid issues like this in the future would be nice though!

  6. added a commit that references this issue on Nov 19, 2021
    ce3f3a5
  7. removed
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    on May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

T-libs-api[DEPRECATED; DO NOT USE]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