Karoy Lorentey

https://github.com/apple/swift-atomics/pull/74 refactored things so that `Bool` now goes through `Int8` atomics instead, even when we're using C atomics.

I suspect testing will uncover an issue with the current definition of `RawRepresentable.AtomicOptionalRepresentation`, but let's land this on current main before tackling that.

Not sure why this was closed. IIUC, the package still has problems building on Windows.

The work in progress to eliminate _AtomicsShims would likely help with this platform, too.

I pieced together some workarounds from the links above in this comment: https://github.com/apple/swift-atomics/issues/79#issuecomment-1492792028 Unfortunately building this on Windows is still failing with a JSON decoding error during -emit-module. I'm giving...

@swift-ci test

Absolutely! This is one area where we're currently missing key functionality, and this will definitely need to be addressed before shipping these types. I've grown to really like using a...

> I suppose you're aware that if your `BitSet` simply used `Int`s for an `Index` type, you could do all of those with the regular slicing subscript? Yes, and that's...

> Sure, but please don't neglect to expose the fundamental partition point-finding operation on which that would be based! Do you think we need to explicitly expose that as a...

> BTW, I hope you're aware of https://github.com/loftware/StandardLibraryProtocolChecks which can be useful for your test coverage. I am! 👍 Have you seen [`_CollectionsTestSupport`](https://github.com/apple/swift-collections/tree/main/Sources/_CollectionsTestSupport)? It operates in the same area, although...