-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
Update wrapping_sh[lr] docs and examples
#149837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2288,6 +2288,13 @@ macro_rules! int_impl { | |
| /// Panic-free bitwise shift-left; yields `self << mask(rhs)`, where `mask` removes | ||
| /// any high-order bits of `rhs` that would cause the shift to exceed the bitwidth of the type. | ||
| /// | ||
| /// Beware that, unlike most other `wrapping_*` methods on integers, this | ||
| /// does *not* give the same result as doing the shift in infinite precision | ||
| /// then truncating as needed. The behaviour matches what shift instructions | ||
| /// do on many processors, and is what the `<<` operator does when overflow | ||
| /// checks are disabled, but numerically it's weird. Consider, instead, | ||
| /// using [`Self::unbounded_shl`] which has nicer behaviour. | ||
| /// | ||
| /// Note that this is *not* the same as a rotate-left; the RHS of a wrapping shift-left is restricted to | ||
| /// the range of the type, rather than the bits shifted out of the LHS being returned to the other end. | ||
| /// The primitive integer types all implement a [`rotate_left`](Self::rotate_left) function, | ||
|
|
@@ -2296,8 +2303,11 @@ macro_rules! int_impl { | |
| /// # Examples | ||
| /// | ||
| /// ``` | ||
| #[doc = concat!("assert_eq!((-1", stringify!($SelfT), ").wrapping_shl(7), -128);")] | ||
| #[doc = concat!("assert_eq!((-1", stringify!($SelfT), ").wrapping_shl(128), -1);")] | ||
| #[doc = concat!("assert_eq!((-1_", stringify!($SelfT), ").wrapping_shl(7), -128);")] | ||
| #[doc = concat!("assert_eq!(42_", stringify!($SelfT), ".wrapping_shl(", stringify!($BITS), "), 42);")] | ||
| #[doc = concat!("assert_eq!(42_", stringify!($SelfT), ".wrapping_shl(1).wrapping_shl(", stringify!($BITS_MINUS_ONE), "), 0);")] | ||
| #[doc = concat!("assert_eq!((-1_", stringify!($SelfT), ").wrapping_shl(128), -1);")] | ||
| #[doc = concat!("assert_eq!(5_", stringify!($SelfT), ".wrapping_shl(1025), 10);")] | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Might be nice to do some of these examples in binary (
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, actually, demonstrating the shift from
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good call; I added a couple more basic examples to show the bits before the extreme examples. |
||
| /// ``` | ||
| #[stable(feature = "num_wrapping", since = "1.2.0")] | ||
| #[rustc_const_stable(feature = "const_int_methods", since = "1.32.0")] | ||
|
|
@@ -2315,6 +2325,13 @@ macro_rules! int_impl { | |
| /// Panic-free bitwise shift-right; yields `self >> mask(rhs)`, where `mask` | ||
| /// removes any high-order bits of `rhs` that would cause the shift to exceed the bitwidth of the type. | ||
| /// | ||
| /// Beware that, unlike most other `wrapping_*` methods on integers, this | ||
| /// does *not* give the same result as doing the shift in infinite precision | ||
| /// then truncating as needed. The behaviour matches what shift instructions | ||
| /// do on many processors, and is what the `>>` operator does when overflow | ||
| /// checks are disabled, but numerically it's weird. Consider, instead, | ||
| /// using [`Self::unbounded_shr`] which has nicer behaviour. | ||
| /// | ||
| /// Note that this is *not* the same as a rotate-right; the RHS of a wrapping shift-right is restricted | ||
| /// to the range of the type, rather than the bits shifted out of the LHS being returned to the other | ||
| /// end. The primitive integer types all implement a [`rotate_right`](Self::rotate_right) function, | ||
|
|
@@ -2323,8 +2340,11 @@ macro_rules! int_impl { | |
| /// # Examples | ||
| /// | ||
| /// ``` | ||
| #[doc = concat!("assert_eq!((-128", stringify!($SelfT), ").wrapping_shr(7), -1);")] | ||
| /// assert_eq!((-128i16).wrapping_shr(64), -128); | ||
| #[doc = concat!("assert_eq!((-128_", stringify!($SelfT), ").wrapping_shr(7), -1);")] | ||
| #[doc = concat!("assert_eq!(42_", stringify!($SelfT), ".wrapping_shr(", stringify!($BITS), "), 42);")] | ||
| #[doc = concat!("assert_eq!(42_", stringify!($SelfT), ".wrapping_shr(1).wrapping_shr(", stringify!($BITS_MINUS_ONE), "), 0);")] | ||
| /// assert_eq!((-128_i16).wrapping_shr(64), -128); | ||
| #[doc = concat!("assert_eq!(10_", stringify!($SelfT), ".wrapping_shr(1025), 5);")] | ||
| /// ``` | ||
| #[stable(feature = "num_wrapping", since = "1.2.0")] | ||
| #[rustc_const_stable(feature = "const_int_methods", since = "1.32.0")] | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait, hm.
Is "nicer" quite right? "More numerical" behavior? "As an integer"? "More logical"? "Is more similar to the mul-by-pow-2 operation you were looking for"?