bitcode
A binary encoder/decoder for Rust (by SoftbearStudios)
bitvec
A crate for managing memory bit by bit (by ferrilab)
| bitcode | bitvec | |
|---|---|---|
| 3 | 17 | |
| 254 | 1,142 | |
| 10.0% | 0.8% | |
| 7.6 | 0.0 | |
| 7 days ago | 17 days ago | |
| Rust | Rust | |
| MIT License | MIT License |
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.
bitcode
Posts with mentions or reviews of bitcode.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-14.
-
bitcode 0.4 release - binary serialization format
bitcode is a new binary serialization format that aims to minimize size while maintaining competitive speed. Since our initial post, we've added a derive macro which unlocks more performance and control than was possible with serde.
-
Announcing bitcode format for serde
Hey u/finn_bear here it is: https://github.com/SoftbearStudios/bitcode/pull/1
bitvec
Posts with mentions or reviews of bitvec.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-14.
-
bitcode 0.4 release - binary serialization format
I was also under the false impression that bitwise encoding was slow. When I first implemented bitcode with bitvec I got performance 20x worse than bincode. After writing my own implementation I was able to get much better performance.
-
An optimized replacement of the infamous std::vector<🅱️ool>
interesting; i'll have to compare this to my rust counterpart. your numbers indicate some clever implementations i'd love to read
-
You need to stop idolizing programming languages.
Not to mention having a lackluster std which causes you to use nonstardard not so well documented crates and a 40K LoC library to do "bit-twiddling" (the lib, https://github.com/bitvecto-rs/bitvec the blog that says "twiddle bits" https://blog.adamchalmers.com/making-a-dns-client/ and for crying out loud the blogger also used the language the author mentioned and I quote "ergonomics AND speed AND correctness")
- bit-twiddling tricks. It's the perfect example of Rust's no-compromises "ergonomics AND speed AND correctness" ideals
-
An Armful of CHERIs: Memory Safety in the processor. Do we still need safe languages with CHERI?
https://github.com/bitvecto-rs/bitvec/issues/135 is a very funny read about how to perform inttoptr with provenance retention
-
bitvec 1.0.0 Released
Technically #135 gives me license to yank affected crates, but since the only exploit is "Miri crashes exactly one test out of the suite" it's not really worth it to be a stickler. Call it a truce
-
What are some creative/advanced uses of macro_rules?
My friend Nika wrote a macro that packs a sequence of 1, 0, … tokens into a correctly structured bit-buffer, adaptable over any register type or bit-ordering, at compile time. It's now basically this whole file
-
Where do I document a published crate?
if you are interested in a user manual, you can use mdbook as well. for an example, my bitvec project uses mdbook (book.toml) and a github action (.github/workflows/gh-pages.yml) to compile the guide and host it as a github pages website. it's slightly more complicated, and i'd like docs.rs to follow hexdoc.pm's example of hosting both api docs and prose, but until then this is a pretty reasonable solution.
-
Idiomatic Way to Validate Struct Field Values
the first one
-
When and how to use traits?
i would browse the standard library, tower, nom, or my own bitvec to see layout and trait/record separation. in particular, std::io and std::net may be of use: io::Read and io::Write are pervasive examples of implementing unixy file-descriptor-like behavior in the type system
What are some alternatives?
When comparing bitcode and bitvec you can also consider the following projects:
msgpack-rust - MessagePack implementation for Rust / msgpack.org[Rust]
nom - Rust parser combinator framework
rust_serialization_benchmark - Benchmarks for rust serialization frameworks
rfcs - RFCs for changes to Rust
dlhn - DLHN implementation for Rust
byteorder - Rust library for reading/writing numbers in big-endian and little-endian.
Weld - Full fake REST API generator written with Rust
time - The most used Rust library for date and time handling.
serde-ndim - Serde support for n-dimensional arrays from self-describing formats
tower - async fn(Request) -> Result<Response, Error>
hardcaml - Hardcaml is an OCaml library for designing hardware.
alacritty - A cross-platform, OpenGL terminal emulator.