safe_arch
Exposes arch-specific intrinsics as safe function (via cfg). (by Lokathor)
tinyvec
Just, really the littlest Vec you could need. So smol. (by Lokathor)
| safe_arch | tinyvec | |
|---|---|---|
| 1 | 4 | |
| 41 | 604 | |
| - | - | |
| 4.5 | 4.4 | |
| 4 months ago | about 1 month ago | |
| Rust | Rust | |
| Apache License 2.0 | 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.
safe_arch
Posts with mentions or reviews of safe_arch.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-22.
-
Rust SIMD native vs. C-Libary
PS: You can use safe_arch to make code a bit more readable. Or even wide.
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.
What are some alternatives?
When comparing safe_arch and tinyvec you can also consider the following projects:
cargo-asm - cargo subcommand showing the assembly or llvm-ir generated for Rust code
heapless - Heapless, `static` friendly data structures
tiny-skia - A tiny Skia subset ported to Rust
trantor - a non-blocking I/O tcp network lib based on c++14/17
wide - A crate to help you go wide. By which I mean use SIMD stuff.
storages-api
bytemuck - A crate for mucking around with piles of bytes
utils - Utility crates used in RustCrypto
totally-safe-transmute
tyrade - A pure functional language for type-level programming in Rust
serde - Serialization framework for Rust
trust-dns - A Rust based DNS client, server, and resolver [Moved to: https://github.com/hickory-dns/hickory-dns]