-
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
[beta] Process backports #51037
[beta] Process backports #51037
Conversation
This comment has been minimized.
This comment has been minimized.
ddf9ce6
to
40d4676
Compare
This comment has been minimized.
This comment has been minimized.
1f83017
to
40d4676
Compare
@petrochenkov #50879 does not apply cleanly on the beta branch, can you please open a new PR with that? |
@pietroalbini |
Thanks @petrochenkov! Current PR status: both #51051 and #51011 needs to be approved before this PR can be merged. |
This comment has been minimized.
This comment has been minimized.
It looks like #51052 is also not beta-accepted yet. |
Also added #51146, which fixes a regression and needs to be approved for backport by the compiler team. |
approved #51146 |
approved #51235 (reading issues really helps in understanding PRs -.-) that should be all of them |
Can someone r+ this? Don't have permissions myself. |
@bors delegate |
@bors r+ |
📌 Commit 64f813d has been approved by |
@bors p=1 (beta backports) |
[beta] Process backports Merged and approved: * #50812: Fix issue #50811 (`NaN > NaN` was true). * #50827: Update LLVM to `56c931901cfb85cd6f7ed44c7d7520a8de1edf97` * #50879: Fix naming conventions for new lints * #51011: rustdoc: hide macro export statements from docs * #51051: prohibit turbofish in `impl Trait` methods * #51052: restore emplacement syntax (obsolete) * #51146: typeck: Do not pass the field check on field error * #51235: remove notion of Implicit derefs from mem-cat r? @ghost
💔 Test failed - status-appveyor |
⌛ Testing commit 52a3735 with merge 145e6d2915c182eb00d33853e68de8259c7a90e9... |
💔 Test failed - status-appveyor |
Ok, this failed again, so I guess it's LLVM fault. |
behavior when NaN is involved.
`PointerKind` is included in `LoanPath` and hence forms part of the equality check; this led to having two unequal paths that both represent `*x`, depending on whether the `*` was inserted automatically or explicitly. Bad mojo. The `note` field, in contrast, is intended more-or-less primarily for this purpose of adding extra data.
If a struct pattern has a field error return an error.
52a3735
to
724cfd8
Compare
Let's try without the LLVM backport. @bors r+ |
📌 Commit 724cfd8 has been approved by |
[beta] Process backports Merged and approved: * #50812: Fix issue #50811 (`NaN > NaN` was true). * #50879: Fix naming conventions for new lints * #51011: rustdoc: hide macro export statements from docs * #51051: prohibit turbofish in impl Trait methods * #51052: restore emplacement syntax (obsolete) * #51146: typeck: Do not pass the field check on field error * #51235: remove notion of Implicit derefs from mem-cat r? @ghost
☀️ Test successful - status-appveyor, status-travis |
Merged and approved:
NaN > NaN
was true). #50812: Fix issue NaN > NaN returns true #50811 (NaN > NaN
was true).impl Trait
methods #51051: prohibit turbofish in impl Trait methodsr? @ghost