-
Notifications
You must be signed in to change notification settings - Fork 13k
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
[beta] Revert "Promote missing_fragment_specifier to hard error #75516" #78146
Conversation
|
@bors rollup=never |
👍 from me on reverting |
@bors r+ |
📌 Commit 62bcdae821e466500edc05ec9b4c5b8311ebfa3c has been approved by |
⌛ Testing commit 62bcdae821e466500edc05ec9b4c5b8311ebfa3c with merge 9bfd49783341567fe637193d584d344fdc8ba76b... |
💔 Test failed - checks-actions |
@bors r- retry |
Looks like some UI tests need an update? |
8e3766d
to
c279138
Compare
This reverts commit 5ba9610.
c279138
to
653c9ee
Compare
@bors r=petrochenkov |
📌 Commit 653c9ee has been approved by |
@bors rollup=never |
☀️ Test successful - checks-actions |
This reverts "Promote missing_fragment_specifier to hard error #75516" on just beta. I would like us to explore a more principled fix, perhaps along the lines @petrochenkov suggested in #76605, on master when we have more time to test it but I don't want us shipping the breakage in the meantime. I don't personally feel comfortable immediately backporting anything more than a revert here.
cc @matklad
This matches #77456 for 1.47 but targets 1.48 (current beta) instead.
r? @petrochenkov