-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Add fetch_and, fetch_or, fetch_nand, fetch_xor to AtomicInt, AtomicUint #12964
Conversation
Could you also add some tests exercising the code? |
Okay, done. |
Looks good to me, and just a few things needed:
|
Squashed, rebased, and passing Travis. |
Gah. Apparently I can't write tests properly at all. Sorry. I've fixed my local build system (without me realizing it, it wasn't running most of the tests, so these failures didn't show up), however, so this shouldn't happen again. |
ping @gereeter, were you able to fix your local checkout? If you're running low on time, I can take over this, I'd love to check it in! |
Okay, this is really weird. It looks like |
Let's not add the |
(#13226) |
I've removed |
[code] make toggleInlayHints understand {off,on}UntilPressed fixes rust-lang#12964
Fix rust-lang#12964 - false positive with `into_iter_without_iter` changelog: FP: `into_iter_without_iter`: No longer lints when the `iter` or `iter_mut` implementation is not within the first `impl` block fixes rust-lang#12964 --- I'm pretty new to this open-source thing, so hopefully I did everything right. Got a little annoyed this false positive was happening in my code and the issue was inactive for two weeks so I thought I'd fix it myself. As an aside, maybe `iter.map(...).next()` could be linted against? I don't see that ever being preferred over `iter.next().map(...)`, and it could've prevented the bug here.
Fixes #12949.