Alexander Payne

By any chance, does the faster old version have `#[inline]` on non-public functions

Hi! We have finally encountered in-the-wild the exact reason I wrote `bitvec` Like This. > This is a long-standing problem in C. GCC, for example, defines that bitfields are laid...

I've been looking around at the implementation and stated goals and I think I'm settling on the notion of passing `Msb0` or `Lsb0` through the macro generation. I've started playing...

`BitVec` corresponds to `Vec`; if you do not have a `Vec`, but instead have an `impl AsRef`, you can use `BitSlice` as a view wrapper over that slice. The [`BitSlice`](https://docs.rs/bitvec/0.21.1/bitvec/slice/index.html)...

Okay the slowdown is extremely weird and obviously unacceptable. I'm *really* intrigued by this use case and will absolutely be digging into it further. From my first impression, it looks...

It's `1.36.0` on current master, as `1.35.0` had not stabilized `MaybeUninit`, which appears in `arrayvec 0.5.1`. # Draft Patch ## `README.md` Place this section anywhere: ~~~markdown ## Minimum Supported Rust...

The "minor versions may increase MSRV" policy is essentially a formalism of what "compiles on stable" actually means. Writing patch-release changes that depend on changes from language minor versions is...

If I'm reading this correctly, the only missing API is the resizing insert? Contains is `.get(idx).unwrap_or(false)`, `.iter_ones()` and the Boolean arithmetic traits work as described. To your favor, I have...

Floating point functions continue to be my long-standing nightmare. Thank you for bringing this to my attention; while I do test against freestanding targets, it *looks* like you're using one...

> a big-endian array of bytes I don't know what this means. I am going to assume that you mean "break a multi-byte integer into bytes, then copy those bytes...