about summary refs log tree commit diff
path: root/src/test/debuginfo/enum-thinlto.rs
diff options
context:
space:
mode:
authorYuki Okushi <huyuumi.dev@gmail.com>2020-01-15 21:51:43 +0900
committerGitHub <noreply@github.com>2020-01-15 21:51:43 +0900
commit89b065dbd2b953ea3ae15ebfb67a799e8b0a3ecc (patch)
treeb64b104fcd7356a07d2e43c431389c559d1921d8 /src/test/debuginfo/enum-thinlto.rs
parente800fe199cbfbbaa46dfa519e46b594512c068be (diff)
parente390b91e5717a338db20360a1ddffa23ba66701d (diff)
downloadrust-89b065dbd2b953ea3ae15ebfb67a799e8b0a3ecc.tar.gz
rust-89b065dbd2b953ea3ae15ebfb67a799e8b0a3ecc.zip
Rollup merge of #67914 - Aaron1011:fix/const-prop-impossible, r=matthewjasper,oli-obk
Don't run const propagation on items with inconsistent bounds

Fixes #67696

Using `#![feature(trivial_bounds)]`, it's possible to write functions
with unsatisfiable 'where' clauses, making them uncallable. However, the
user can act as if these 'where' clauses are true inside the body of the
function, leading to code that would normally be impossible to write.

Since const propgation can run even without any user-written calls to a
function, we need to explcitly check for these uncallable functions.
Diffstat (limited to 'src/test/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions