You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not quickly finding the PR which introduced the new impls, but it looks like some AsRef impls were added in 1.51, and those are causing breakage as determined through beta crater. Usually we don't do anything here, but would be good to at least ping authors.
searched nightlies: from nightly-2021-01-01 to nightly-2021-03-03
regressed nightly: nightly-2021-01-26
searched commits: from 1d0d76f to f4eb5d9
regressed commit: d3163e9
Hm, none of the PRs in that rollup should affect AsRef for String, which is what all these regressions are about. There's only one trait implementation added in that rollup: impl Error for &(impl Error).
Activity
apiraino commentedon Mar 3, 2021
I've tried bisecting this issue (if it helps):
searched nightlies: from nightly-2021-01-01 to nightly-2021-03-03
regressed nightly: nightly-2021-01-26
searched commits: from 1d0d76f to f4eb5d9
regressed commit: d3163e9
bisected with cargo-bisect-rustc v0.6.0
Host triple: x86_64-unknown-linux-gnu
Reproduce with:
somewhere in this rollup #81355
m-ou-se commentedon Mar 3, 2021
Hm, none of the PRs in that rollup should affect AsRef for String, which is what all these regressions are about. There's only one trait implementation added in that rollup:
impl Error for &(impl Error).JohnTitor commentedon Mar 5, 2021
This shows the regression (playground):
And yes, confirmed that #75180 is the cause.
LeSeulArtichaut commentedon Mar 5, 2021
It looks like those were expected regressions (see #75180 (comment)).
JohnTitor commentedon Mar 22, 2021
Triage: Close this issue as an acceptable regression, we mentioned it in #75180 (comment) and consider it acceptable through FCP.