venial
miniserde
Our great sponsors
venial | miniserde | |
---|---|---|
5 | 4 | |
181 | 724 | |
- | - | |
7.3 | 7.7 | |
about 1 month ago | 10 days 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.
venial
-
Improving build times for derive macros by 3x or more
How myn compares to https://github.com/PoignardAzur/venial?
-
Yet another command line argument parser: bpaf 0.5.5
venial is supposed to be a lighter weight alternative to syn that might work. Besides level of maturity, the biggest risk is slowing things down for people already using syn but I think there was a claim that it wasn't noticeable.
- venial 0.4 - A lightweight alternative to syn
- venial 0.2 - A lightweight alternative to syn
- venial 0.1 - A lightweight alternative to syn
miniserde
-
Hey Rustaceans! Got a question? Ask here (8/2023)!
It's pretty common to avoid macros as they can seem too magical a lot of the time. And with traits, there's experiments like miniserde which specifically avoid monomorphization overhead. I also see people who want to avoid having lots of dependencies relatively often.
-
venial 0.1 - A lightweight alternative to syn
Right now, the next step would be to try to reimplement miniserde with venial, and publish benchmarks.
- Rust takes a major step forward as Linux's second official language
-
The Serde Rust Framework
The only downside is compile time bloat.
Serde generates heaps and heaps of generic code. This gets optimized away to be very efficient, but it can be quite cumbersome.
Ever tried working on a crate with hundreds or thousands of de/serializable types? Compile times shoot through the roof really quickly.
The maintainer of serde also created `miniserde` [1], which uses dynamic dispatch and can have 4x compile time improvements.
Due to Rusts lack of orphan instances you really depend on a pervasive standard for serializiation which is used by all libraries, so the ecosystem is really locked in to serde by now.
[1] https://github.com/dtolnay/miniserde
What are some alternatives?
darling - A Rust proc-macro attribute parser
nanoserde - Serialisation library with zero dependencies
ComLightInterop - Cross-platform COM interop library for .NET Core 2.1 or newer
bpaf - Command line parser with applicative interface
serde_v8 - Moved to https://github.com/denoland/deno
rustc-dev-guide - A guide to how rustc works and how to contribute to it.
pfr - std::tuple like methods for user defined types without any macro or boilerplate code
argparse-rosetta-rs - Comparing argparse APIs
serde - Serialization framework for Rust
validator - Simple validation for Rust structs
sapio - A Bitcoin Programming Language