about summary refs log tree commit diff
path: root/src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2020-01-27 08:42:56 +0000
committerbors <bors@rust-lang.org>2020-01-27 08:42:56 +0000
commit1d5f6d41e140a3d6a9c6584d555bc09f10222d24 (patch)
treea8563b9552a092e5660b1a3cde97de357dbd6a80 /src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs
parent320ada6479b3e29c7d9a66bc56ac44c2d2b57566 (diff)
parent783a7dc8ed03a38910b9ea5ded11139616dfa67b (diff)
downloadrust-1d5f6d41e140a3d6a9c6584d555bc09f10222d24.tar.gz
rust-1d5f6d41e140a3d6a9c6584d555bc09f10222d24.zip
Auto merge of #68165 - thomcc:lt_ones, r=sfackler
Add leading_ones and trailing_ones methods to the primitive integer types

I was surprised these were missing (given that `leading_zeros` and `trailing_zeros` exist), and they seem trivial and hopefully not controversial.

Note that there's some precedent in that `count_ones` and `count_zeros` are both supported even though only one of these has an intrinsic.

I'm not sure if these need a `rustc_const_unstable` flag (the tests don't seem to mind that it's missing). I just made them const, since there's not really any reason for these to be non-const when the `_zeros` variants are const.

Note: My understanding is trivial stuff like (hopefully) this can land without an RFC, but I'm not fully sure about the process though. Questions like "when does the tracking issue get filed?", are a total mystery to me. So, any guidance is appreciated, and sorry in advance if I should have gone through some more involved process for this.
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs')
0 files changed, 0 insertions, 0 deletions