Fix soundness bug described in #29859#35745
Conversation
|
(rust_highfive has picked a reviewer for you, use r? to override) |
|
☔ The latest upstream changes (presumably #35605) made this pull request unmergeable. Please resolve the merge conflicts. |
src/librustc_typeck/check/wfcheck.rs
Outdated
87ccbb9 to
da2451e
Compare
src/librustc_typeck/check/wfcheck.rs
Outdated
There was a problem hiding this comment.
Nit: s/can not/cannot/, also let's make if impl Trait for .. and not unsafe impl Trait
|
@bors r+ |
|
📌 Commit 26c6439 has been approved by |
6da7b17 to
feff760
Compare
|
@bors r=nikomatsakis |
|
📌 Commit feff760 has been approved by |
feff760 to
fad75e6
Compare
|
@bors r=nikomatsakis |
|
Thanks @alexcrichton, not really sure why it wasn't building, been moving apartments this weekend so haven't had any time to chase it down. |
|
Huh. What is happening with bors here. :) |
|
@bors r- |
|
@bors r+ |
|
📌 Commit fad75e6 has been approved by |
|
⌛ Testing commit fad75e6 with merge 71b0f61... |
|
💔 Test failed - auto-mac-64-opt |
01d509e to
dba5cbe
Compare
|
@bors r- |
|
@bors r=nikomatsakis |
|
📌 Commit dba5cbe has been approved by |
Fix soundness bug described in #29859 This is an attempt at fixing the problems described in #29859 based on an IRC conversation between @nikomatsakis and I today. I'm waiting on a full build to come back, otherwise both tests trigger the correct error.
|
💔 Test failed - auto-mac-64-opt-rustbuild |
|
@bors retry |
|
⌛ Testing commit dba5cbe with merge e98a1a4... |
|
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
dba5cbe to
9510add
Compare
|
Travis failure: |
|
@bors r+ |
|
📌 Commit a254282 has been approved by |
|
⌛ Testing commit a254282 with merge 384969e... |
|
💔 Test failed - auto-linux-32-nopt-t |
|
@bors: retry On Thu, Sep 8, 2016 at 7:20 AM, bors notifications@github.com wrote:
|
Fix soundness bug described in #29859 This is an attempt at fixing the problems described in #29859 based on an IRC conversation between @nikomatsakis and I today. I'm waiting on a full build to come back, otherwise both tests trigger the correct error.
This is an attempt at fixing the problems described in #29859 based on an IRC conversation between @nikomatsakis and I today. I'm waiting on a full build to come back, otherwise both tests trigger the correct error.