diff options
| author | bors <bors@rust-lang.org> | 2017-01-05 11:06:10 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2017-01-05 11:06:10 +0000 |
| commit | 2f56207b1283857de92537288893e8d428551a02 (patch) | |
| tree | b358541c2acb4bdcbfd110efa476e87f34b6b9e1 /src/liballoc_system | |
| parent | 26e2ee00f94f1e9c571858a6a49becc71807860d (diff) | |
| parent | fbdadcbed4c9a04b909246a8145e3e722c63525b (diff) | |
| download | rust-2f56207b1283857de92537288893e8d428551a02.tar.gz rust-2f56207b1283857de92537288893e8d428551a02.zip | |
Auto merge of #38776 - eddyb:unsigned-means-unsigned, r=pnkfelix
Properly ban the negation of unsigned integers in type-checking. Lint-time banning of unsigned negation appears to be vestigial from a time it was feature-gated. But now it always errors and we do have the ability to deref the checking of e.g. `-0`, through the trait obligation fulfillment context, which will only succeed/error when the `0` gets inferred to a specific type. The two removed tests are the main reason for finally cleaning this up, they need changing all the time when refactoring the HIR-based `rustc_const_eval` and/or `rustc_passes::consts`, as warnings pile up.
Diffstat (limited to 'src/liballoc_system')
0 files changed, 0 insertions, 0 deletions