diff options
| author | Dylan DPC <99973273+Dylan-DPC@users.noreply.github.com> | 2022-09-29 18:13:19 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-09-29 18:13:19 +0530 |
| commit | 609152aa8a9faf2b8177dacd6d673b4bc06d1eda (patch) | |
| tree | 54ea9a0275bdfa5ef0c850f3dc3100a11068051e /library/std/src/sys/unix/stack_overflow.rs | |
| parent | 1be9ec54437c396acf64ed9be75270752ab5abad (diff) | |
| parent | ceb53a3c4fa9f0c3da7b7e6d24011dee1d15ad09 (diff) | |
| download | rust-609152aa8a9faf2b8177dacd6d673b4bc06d1eda.tar.gz rust-609152aa8a9faf2b8177dacd6d673b4bc06d1eda.zip | |
Rollup merge of #102342 - jmillikin:nonzero-negation, r=scottmcm
Add negation methods for signed non-zero integers.
Performing negation with defined wrapping semantics (such as `wrapping_neg()`) on a non-zero integer currently requires unpacking to a primitive and re-wrapping. Since negation of non-zero signed integers always produces a non-zero result, it is safe to implement the various `*_neg()` methods for `NonZeroI{N}`.
I'm not sure what to do about the `#[unstable(..., issue = "none")]` here -- should I file a tracking issue, or is that handled by the Rust dev team?
ACP: https://github.com/rust-lang/libs-team/issues/105
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions