Skip to content

regression: array methods unstable feature use #78140

Closed

Description

@Mark-Simulacrum

Several crates are erroring on as_slice/as_mut_slice being added to the array types (unstably).

I suspect this is because method resolution is now seeing the method on arrays, whereas previously we derefed to &mut [T] and then there was a trait impl on that? There was another similar issue recently, but I forget what the resolution there was.

cc #76118

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 Oct 20, 2020
  2. added
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    on Oct 20, 2020
  3. added this to the 1.48.0 milestone on Oct 20, 2020
  4. 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 Oct 21, 2020
  5. camelid commented on Oct 21, 2020

    @camelid
    Member

    Relevant wg-prioritization discussion.

  6. eddyb commented on Nov 6, 2020

    @eddyb
    Contributor

    Shouldn't #48552 prevent this from being an issue at all? Do we need to extend it in some way?
    cc @nikomatsakis @pnkfelix

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

    P-highHigh priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.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