-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert PR 81473 to resolve (on mainline) issues 81626 and 81658. #86212
Revert PR 81473 to resolve (on mainline) issues 81626 and 81658. #86212
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
r=me but looks like there's CI trouble here, and presumably we'll need another backport as this unfortunately didn't land in time for 1.54 branching |
Triage: |
Beta-nominated for 1.54, as this will land in 1.55. |
☔ The latest upstream changes (presumably #87129) made this pull request unmergeable. Please resolve the merge conflicts. |
Hmm. Do I delete the unused method, or just |
I expect these two methods to come back very soon; noise of removing them to satisfy lint seems wrong.
7ae061c
to
b6e9d06
Compare
@bors r=simulacrum also, unilaterally approving for beta backport. |
📌 Commit ee2bb1f has been approved by |
@bors p=1 |
☀️ Test successful - checks-actions |
…warn-write-only-fields, r=Mark-Simulacrum Beta targetted revert 81473 warn write only fields beta backport of PR rust-lang#86212
This is a nightly-targetted variant of PR #83171
The intent is to just address issue #81658 on all release channels, rather that keep repeatedly reverting PR #83171 on beta.
However, our intent is also to reland PR #83171 after we have addressed issue #81658 , most likely by coupling the re-landing of PR #83171 with an enhancement like PR #83004