Panic when using mem::uninitialized or mem::zeroed on an uninhabited type#54667
Panic when using mem::uninitialized or mem::zeroed on an uninhabited type#54667bors merged 11 commits intorust-lang:masterfrom
Conversation
|
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
|
@bors try |
|
⌛ Trying commit a1a74ab5ad7fae002fe65b388a19be7275536871 with merge cd661db2bccbe284334ee486254891e2858a667a... |
|
💔 Test failed - status-travis |
|
It got cancelled by another try build. Try again. @bors try |
|
@bors retry |
|
⌛ Trying commit a1a74ab5ad7fae002fe65b388a19be7275536871 with merge 31ec4bcad01a3a5f6214474912ec7f53478414d7... |
This comment has been minimized.
This comment has been minimized.
|
Dang, it's that gdb test again. :/ @japaric any idea? |
|
Oh I see. I put all commits related to that test into the other PR because I though it was only about the changed data structures. But it is also about this panic. |
a1a74ab to
c64749b
Compare
|
@rust-timer build 31ec4bcad01a3a5f6214474912ec7f53478414d7 |
|
Success: Queued 31ec4bcad01a3a5f6214474912ec7f53478414d7 with parent 7e7bc06, comparison URL. |
|
Perf came back; looks clean to me. |
This comment has been minimized.
This comment has been minimized.
c64749b to
dd65d73
Compare
|
@bors r+ |
|
📌 Commit dd65d73 has been approved by |
|
⌛ Testing commit dd65d73 with merge 48e45914f2f6dc7499fee2c031c06cf4b4c5ddf7... |
|
@bors r+ |
|
💡 This pull request was already approved, no need to approve it again.
|
|
📌 Commit dd65d73 has been approved by |
|
☀️ Test successful - status-appveyor, status-travis |
All code by @japaric. This re-submits one half of #53508. This is likely not the one that introduced the perf regression, but just to be sure I'll do a perf run anyway.