tinyvec
Just, really the littlest Vec you could need. So smol. (by Lokathor)
| tinyvec | storages-api | |
|---|---|---|
| 4 | 5 | |
| 605 | 9 | |
| - | - | |
| 4.4 | 0.0 | |
| about 2 months ago | 8 months ago | |
| Rust | Rust | |
| Apache License 2.0 | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tinyvec
Posts with mentions or reviews of tinyvec.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-01.
-
The Better Alternative to Lifetime GATs
funny indeed. i changed all my projects to use tinyvec
-
"pure safe crates"
I've seen the cost of zeroing memory be measurable, or maybe significant enough to care about, but I've never seen 90% of cycles spent on it, the only case I know of that gets close is creating an empty TinyVec versus an empty SmallVec with an inline buffer of 256 bytes. In my opinion that's an unreasonably large inline buffer. At inline buffers of 128 bytes and below, the overhead is less than 50%, and that's on a microbenchmark of the Default impl; the effect is rapidly diluted in a real program.
-
single-producer single-consumer concurrent queue
My point is that "implementation that doesn't use unsafe" is not necessarily always slower than "implementation that does use unsafe". Often people assume that this is the case, and it isn't. tinyvec currently beats smallvec in more than a few benchmarks. Not all, but some. And this sometimes visible to users. The point is that if you want speed, you don't necessarily need to give up any safety at all. Most differences in performance are due to the amount of effort or expertise that has been spent on the codebase, not the amount of unsafe in it.
-
Now that the long-awaited const generics (MVP) have come to stable in 1.51, what crates are going to gain the most from it?
https://github.com/Lokathor/tinyvec will definitely benefit, although not as much as something currently relying on typenum.
storages-api
Posts with mentions or reviews of storages-api.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-04.
-
What’s the status of the Storage proposal?
I think here you can find the new repository as there are commits from yesterday. Also this is probably the most recent discussion about the proposal.
-
Fellow Rust enthusiasts: What "sucks" about Rust?
I believe SSO could be solved, in part, with the Storage proposal I made a while ago, which Christopher Duram refined in his storages-api repository.
-
Taking ownership of memory, how straightforward is it?
/u/CAD97 is currently exploring whether storages would be a better alternative: feasibility, API impacts, etc... for example see https://github.com/CAD97/storages-api for a much revised API compared to my initial proposal.
-
Specialized Allocators for containers
This sounds like a less refined version of the storages API: https://github.com/CAD97/storages-api
-
The Better Alternative to Lifetime GATs
The unfortunate asterisk to this is my work on the Storage api; with that abstraction Vec itself could be the small vector type rather than duplicating the entire API onto a second type.
What are some alternatives?
When comparing tinyvec and storages-api you can also consider the following projects:
heapless - Heapless, `static` friendly data structures
dislike-in-rust - A list of the few things I don't like about rust
trantor - a non-blocking I/O tcp network lib based on c++14/17
pollster - A minimal async executor that lets you block on a future
utils - Utility crates used in RustCrypto
storage - An exploration of Storages
totally-safe-transmute
any_vec - Rust type erased vector.
tyrade - A pure functional language for type-level programming in Rust
unsafe-code-guidelines - Forum for discussion about what unsafe code can and can't do
serde - Serialization framework for Rust
rust - Empowering everyone to build reliable and efficient software.