Thom Chiovoloni
Thom Chiovoloni
I'm using bstr to help parse a few formats, some of them are text (but not necessarily utf8) and some of them are binary but contain strings. I have a...
`ByteSlice::trim` (and related) are not competitive with libstd's in the case that the whitespace is ASCII. The difference is as much as 50%, and is something I noticed when moving...
In the distant future, when `bstr` can use const generics, the following reduces the amount of `B(b"blah")` you need to to literals do by a decent amount, letting you use...
I think it would be good to expose a free function from `bstr` that exposes some decoding-specific information about what a given byte means in the context of utf8. Accessing...
I don't have a concrete use for this, but when writing the byteset code it occurred to me that people might want to use it for e.g. searching for the...
- Add mutex.rs (old) - fix warnings on macos - Remove `#[derive(Debug)]` from types that are `c_void` wrappers (if it ever ran it would be unsound, since it would read...
Unsure why CI is failing on 1.43. Cargo is failing with `error reading from the zlib stream; class=Zlib (5)`: ``` cargo test --no-default-features --verbose shell: /usr/bin/bash -e {0} env: RUST_BACKTRACE:...
That is: a thread-unsafe (e.g. `!Send`) equivalent to `ArcStr`. `std::rc::Rc` would be to `RcStr` as `std::sync::Arc` is to `ArcStr`). It would avoid needing to use atomic operations, but otherwise would...
We could define a custom trait (see how hashbrown does this) to support it prior to the unstable trait landing. This would (at the very least) allow testing allocation fallibility[^1],...
From Readme: Essentially this will be an 8-byte wrapper around `ArcStr` that allows storing small 7b-or-fewer strings inline, without allocation. It will be 8 bytes on 32-bit and 64-bit platforms...