Builder Derive Macro Documentation

The Builder derive macro is used to generate builder methods for structs in Rust, its biggest feature in this crate is that it provides compile-time validation on the struct. The user can employ several configurations that define the validity of of a complex struct, and it is checked before the struct is ever created.

## Prerequisites

To use the Builder derive macro, you should have the const_typed_builder crate added to your project's dependencies in your Cargo.toml file:

toml [dependencies] const_typed_builder = "0.2"

Also, make sure you have the following import statements in your code:

rust use const_typed_builder::Builder;

Overview

Simple example

This derive: ```rust use consttypedbuilder::Builder;

[derive(Debug, Builder)]

pub struct Foo { bar: String, } Expands to this code: rust use consttypedbuilder::Builder;

[derive(Debug)]

pub struct Foo { bar: String, } impl Builder for Foo { type BuilderImpl = FooBuilder; fn builder() -> Self::BuilderImpl { Self::BuilderImpl::new() } }

[derive(Debug)]

pub struct FooBuilder { data: FooData, } impl FooBuilder { pub fn new() -> FooBuilder { Self::default() } } impl Default for FooBuilder { fn default() -> Self { FooBuilder { data: FooData::default(), } } } impl FooBuilder { pub fn bar(self, bar: String) -> FooBuilder { let mut data = self.data; data.bar = Some(bar); FooBuilder { data } } } impl FooBuilder { pub fn build(self) -> Foo { self.data.into() } }

[derive(Debug)]

pub struct FooData { pub bar: Option, } impl From for Foo { fn from(data: FooData) -> Foo { Foo { bar: data.bar.unwrap(), } } } impl Default for FooData { fn default() -> Self { FooData { bar: None } } } ```

[!NOTE] Checking the validity of each field is a problem directly related to SAT, which is an NP-complete problem. This has effect especially the grouped fields. The current default implementation for checking the validity of grouped fields is brute_force, and this implementation currently has a complexity of $O(2^g)$ where $g$ is the amount of grouped variables. This is not a problem with a couple of fields, but it might impact compile time significantly with more fields. This can be still optimized significantly. Future editions might improve on this complexity.

Another implementation is compiler. I haven't tested its speed increase yet, but it might have an issue. Although I haven't been able to recreate the issue yet, it seems that const values aren't guaranteed to be evaluated at compile time. This creates the issue that the group verification is not guaranteed to fail during compile-time.

Users can opt in to the compiler solver, by adding #[builder(solver = compiler)] above the struct. I'm not making any guarantees on its performance.

Anyone who would like to help, and add a SAT solver as a dependency (behind a feature flag) is welcome to do so!

Inspirations

Builder macros have been done before, but not exactly what I needed for my use case. Also look into derive_builder and typed-builder. Those projects are currently way more mature, but anyone willing to test this crate is currently a godsend.