bitvec VS validator

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.

interesting; i'll have to compare this to my rust counterpart. your numbers indicate some clever implementations i'd love to read

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")

https://github.com/bitvecto-rs/bitvec/issues/135 is a very funny read about how to perform inttoptr with provenance retention

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

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

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.

the first one

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

(That's how certain kinds of extensibility work in the validator crate. You just impl a method and validator won't care where it comes from as long as it's in scope because it's built using declarative macros.)

The rust proc macro system is my absolute favorite feature of the language. One of my other favorite libraries is https://github.com/Keats/validator

Hi! I'm happy to announce the release of garde. In summary, this is a rewrite of the validator crate.

Validator : Macros 1.1 custom derive to simplify struct validation inspired by marshmallow and Django validators

https://github.com/Keats/validator needs some help, it's a validation library that easily plugs into Web Development.

(The validate attribute is from the validator crate.)

Would love to use it in https://github.com/Keats/validator when it's ready!

Actually, /u/mehcode just reminded me that this exists: https://github.com/Keats/validator