diff options
| author | bors <bors@rust-lang.org> | 2015-10-18 11:09:03 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-10-18 11:09:03 +0000 |
| commit | 3f2ad610a8e33a1525897afb04774e53aaad3fc2 (patch) | |
| tree | 5b74580947c826daa4c246d740ff208522c9ae44 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 9d7c5e5d3d355a3980e3c598456b616942bfb6d9 (diff) | |
| parent | 09d3adf52eaf6e411b49d26af7d347406f563557 (diff) | |
| download | rust-3f2ad610a8e33a1525897afb04774e53aaad3fc2.tar.gz rust-3f2ad610a8e33a1525897afb04774e53aaad3fc2.zip | |
Auto merge of #28845 - oli-obk:rfc1229, r=pnkfelix
This PR turns statically known erroneous code (e.g. numeric overflow) into a warning and continues normal code-generation to emit the same code that would have been generated without `check_const` detecting that the result can be computed at compile-time. <del>It's not done yet, as I don't know how to properly emit a lint from trans. I can't seem to extract the real lint level of the item the erroneous expression is in.</del> It's an unconditional warning now. r? @pnkfelix cc @nikomatsakis * [RFC 1229 text](https://github.com/rust-lang/rfcs/blob/master/text/1229-compile-time-asserts.md) * RFC PR: rust-lang/rfcs#1229 * tracking issue: https://github.com/rust-lang/rust/issues/28238
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions