tinyvec
tinyvec copied to clipboard
Lokathor
Just, really the littlest Vec you could need. So smol.
Implement two things that were tracked in TODO comments, although only one appears to be in live code: using `core::mem::take` rather than a reimplementation of it when Rust 1.40 is...
This expression tries to construct an `ArrayVec` with element type `(f32, f32)` but cannot compile: ```rust let a: ArrayVec = array_vec!((2.0, 2.0), (2.0, 2.0), (2.0, 2.0)); ``` The error goes...
This seems like a logical extension of the existing functionality. Of course, you could manually do the bounds check, but that's error-prone and in performance-sensitive applications could be concerning.
I have been working on Rust compiler performance, guided by [this analysis document](https://hackmd.io/mxdn4U58Su-UQXwzOHpHag) that looks at compilation of 800 popular crates. It identifies `tinyvec` as an interesting case, being the...
* [ ] ArrayVec * [ ] TinyVec Waiting on https://github.com/rust-lang/rust/issues/43244, though we could add this behind a feature gate before that if we like.
The same way, as you have serde traits under `serde` feature, you can add [borsh](https://github.com/near/borsh-rs) traits under `borsh` feature.
Would y'all accept a PR that implements `std::io::Write` for u8-based TinyVecs? If so, I'd be thrilled to submit it.
The current `array_vec` macro seems to have problems with some inputs. If you give it the following input ```rust // Somewhere in your codebase struct T(i32); impl T { fn...
Hi :wave: I maintain a [crate that abstracts over growable vectors](https://artichoke.github.io/artichoke/spinoso_array/) such that they would be appropriate for implementing a Ruby `Array`. This crate had backends for `Vec` and `SmallVec`....
Right now we have a pretty good fuzzing setup for TinyVec and ArrayVec types that has found [a](https://github.com/Lokathor/tinyvec/pull/14) [number](https://github.com/Lokathor/tinyvec/pull/15) [of](https://github.com/Lokathor/tinyvec/pull/16) [bugs](https://github.com/rust-lang/rust/issues/74909). We should extend this to cover SliceVec and ArraySet...
