bon

yes. tests test what? logic. logic = types (proven). so stronger type system less test needs to be written. more, if proc macro or build.rs can execute logic, based on parsed """types"""(partial info only), we can extend type systems with custom logic (and panic at compile time and/or startup time if usage violation detected). on top of that, add fail fast (fail at compile time, build time or start up time) and newtype and errors-part-of-api culture; and lack of late binding (dyn is very limited use, no runtime reflection), and we get even less reasons to write tests. some examples of industrial """typing"""(eDSLs, construction time) solutions in rust : - https://github.com/elastio/bon - https://github.com/contextgeneric/cgp - https://github.com/paritytech/orchestra - https://git.pipapo.org/cehteh/linear_type.git sure we need write tests,

Blog post: https://elastio.github.io/bon/blog/bon-builder-generator-v2-... GitHub repo of the crate: https://github.com/elastio/bon --- If you are new to `bon`, here is a quick example of it's API. `bon` can generate a builder from a function, effectively solving the problem of named function arguments in Rust described in [the introduction blog post](https://elastio.github.io/bon/blog/how-to-do-named-function-...). ```rust use bon::builder; #[builder] fn greet(name: &str, age: u32) -> String { format!("Hello {name} with age {age}!") } let greeting = greet() .name("Bon") .age(24) .call(); assert_eq!(greeting, "Hello Bon with age 24!"); ``` It also supports generating builders from structs and associated methods. See the [Github repo](https://github.com/elastio/bon) and the [crate overview guide](https://elastio.github