-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Fix various bugs around empty structs and patterns #29383
Conversation
r? @pnkfelix (rust_highfive has picked a reviewer for you, use r? to override) |
Heh, yeah, I like to do |
This PR looks fine to me. It does need a crater run. (I have not yet successfully run crater but I'm wiling to give it another shot.) |
☔ The latest upstream changes (presumably #28846) made this pull request unmergeable. Please resolve the merge conflicts. |
Rebased. |
@petrochenkov great; I am seeing if I can do a crater run now with it. |
I've made a new |
☔ The latest upstream changes (presumably #29217) made this pull request unmergeable. Please resolve the merge conflicts. |
Rebased. |
☔ The latest upstream changes (presumably #29581) made this pull request unmergeable. Please resolve the merge conflicts. |
@petrochenkov thanks for rebasing |
I did a crater run (on the revisions from before the rebase).
crater results here: https://gist.github.com/pnkfelix/4b800d1faf17eb494d8e Update: I just looked at those results again, and realized that, if I understand them correctly, they are saying that all crates failed to build on both of my compilers. :( I'm not quite sure what I did wrong, if anything. I'll try a new run on the rebased versions. |
Update: see above comment. The aforementioned crater run seemed problematic, not b/c of this PR, but probably user error. |
Rebased. |
☔ The latest upstream changes (presumably #29763) made this pull request unmergeable. Please resolve the merge conflicts. |
Rebased. @alexcrichton, could you run crater on this? |
Starting a crater run. |
☔ The latest upstream changes (presumably #29387) made this pull request unmergeable. Please resolve the merge conflicts. |
Crater reports eight root regressions with as many as up to 34. I glanced at the root ones and they at least all look legitimate. Perhaps that error could be a warning for a few cycles? Seems like a good bugfix to have, but may be good to give fair warning. |
Rebased. |
ping @pnkfelix |
@bors r+ |
📌 Commit af96402 has been approved by |
⌛ Testing commit af96402 with merge f0fcef8... |
💔 Test failed - auto-mac-32-opt |
Needs retry |
@bors retry |
Fixes #28692 Fixes #28992 Fixes some other similar issues (see the tests) [breaking-change], needs crater run (cc @brson or @alexcrichton ) The pattern with parens `UnitVariant(..)` for unit variants seems to be popular in rustc (see the second commit), but mostly used by one person (@nikomatsakis), according to git blame. If it causes breakage on crates.io I'll add an exceptional case for it.
It looks like it's a breaking change anyway, conv
|
…structs See rust-lang/rust#29383 for the breaking change.
Hm, the warning should not affect exhaustiveness check, I'll investigate what happens. |
I apologise if I'm pointing to the wrong PR, but it seems related. |
Fixes #28692
Fixes #28992
Fixes some other similar issues (see the tests)
[breaking-change], needs crater run (cc @brson or @alexcrichton )
The pattern with parens
UnitVariant(..)
for unit variants seems to be popular in rustc (see the second commit), but mostly used by one person (@nikomatsakis), according to git blame. If it causes breakage on crates.io I'll add an exceptional case for it.