bitvec
case-studies
Our great sponsors
bitvec | case-studies | |
---|---|---|
17 | 11 | |
1,138 | 1,602 | |
1.5% | - | |
0.0 | 3.8 | |
11 days ago | about 1 month ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
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.
bitvec
-
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
case-studies
-
::lending-iterator — Lending/streaming Iterators on Stable Rust (and a pinch of HKT)
Luckily there is a workaround to emulate such a definition, which dtolnay discovered and explained here: https://github.com/dtolnay/case-studies/tree/b9802f6df8dc8e54970b83fb9af6df923b46abf5/unit-type-parameters.
-
Hey Rustaceans! Got a question? Ask here! (17/2022)!
I think they are talking about this one trick which the devs don't want you to know about. Note that while it looks like specialization, it works only in a few very limited cases and is quite fragile, so it's a hack, not a substitute for the real feature.
-
Any good resources for learning Rust macros?
Also I suggest his case studies repo since you are looking at what is possible: https://github.com/dtolnay/case-studies
-
What are some creative/advanced uses of macro_rules?
/u/dtolnay has a great case studies repository.
-
Hey Rustaceans! Got an easy question? Ask here (29/2021)!
Once you have the basics down, read dtolnay's case studies. They show how to do advanced stuff with easy macros.
-
println use `Debug` if argument is not `Display`
If you were writing your own println macro, you might be able to get away with this kind of hack: https://github.com/dtolnay/case-studies/blob/master/autoref-specialization/README.md
-
Hey Rustaceans! Got an easy question? Ask here (11/2021)!
You can use "Autoref-based stable specialization" or use/mimic the impls crate.
-
Why I gave up on Rust (for now)
With a subset of specialization likely riding the trains soon and a workaround available, why would you give up?
-
Hey Rustaceans! Got an easy question? Ask here (10/2021)!
this works since values and types are in different namespaces (see: Rusts Universes or dtolnay's Case Study about "Unit struct with type parameters")
-
Hey Rustaceans! Got an easy question? Ask here (53/2020)!
To do this with traits you would need specialization but since you are using macros you should be able to use "Autoref-based stable specialization". Here is a playground which uses the latter approach to implement the wanted macro without using any nightly features.
What are some alternatives?
nom - Rust parser combinator framework
rocket-auth-login - Authentication and login processing for Rust's Rocket web framework. Demonstrates a working example of how to authenticate users and process login as well as how to handle logging out.
rfcs - RFCs for changes to Rust
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
time - The most used Rust library for date and time handling.
xargo - The sysroot manager that lets you build and customize `std`
byteorder - Rust library for reading/writing numbers in big-endian and little-endian.
proc-macro-crate - `$crate` in procedural macros.
tower - async fn(Request) -> Result<Response, Error>
parquet2 - Fastest and safest Rust implementation of parquet. `unsafe` free. Integration-tested against pyarrow
hardcaml - Hardcaml is an OCaml library for designing hardware.
cargo-expand - Subcommand to show result of macro expansion