Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Very nice to see non-utf8 supported here. This is now looking like a very good niche in the tradeoffs among argument parsers (see: https://github.com/rosetta-rs/argparse-rosetta-rs). I guess I should try it first, but this is looking like an obvious recommendation as the "default choice" of argument parser to me.
https://github.com/pacak/bpaf/blob/master/examples/rectangle.rs#L32 (with a small cosmetic issue - https://github.com/pacak/bpaf/issues/47) - thank you for your crazy idea <3 :)
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.
Do you have links to any good info about how much rustc reuses from previous runs? This is the first time i hear about reuse at the function level. I guess the rustc-dev-guide would be a good place for me to start?
Other than having to define a group? I think it's only logical if you want your users to see something as a logical group - to have it as a group inside the code as well. Like cargo defines all those logical groups for features, timings, etc: https://github.com/rust-lang/cargo/blob/master/src/bin/cargo/commands/build.rs
Related posts
- Cargo has never frustrated me like npm or pip has. Does Cargo ever get frustrating? Does anyone ever find themselves in dependency hell?
- Learning Rust by Building a CLI App
- Is Rust's cargo-edit crate still relevant?
- TIL about cargo add
- Cargo: Namespaced and weak dependency features have been stabilized