structural-typing 0.1.9

//! # Structural Typing for Rust
//!
//! Structural typing separates schemas (what fields can exist) from selections (what fields must be
//! present). Optionality is context-dependent—a name is always a string, but different contexts may
//! or may not require it. Instead of creating separate types for each context (`CreateUser`,
//! `UpdateUser`, `DBUser`...) or using `Option<T>` everywhere, define your schema once and use
//! generic trait bounds for context-specific requirements—all verified at compile time.
//!
//! This design is inspired by Rich Hickey's [`Maybe Not`](https://www.youtube.com/watch?v=YR5WdGrpoug)
//! talk, which articulates the principle of separating attribute definitions from their use in aggregates,
//! along with ideas from TypeScript's structural types and RDF's independent attributes.
//!
//! ## Installation
//!
//! ```toml
//! [dependencies]
//! structural-typing = "0.1.9"
//! derive-where = "1.6"  # For deriving traits on structural types
//! ```
//!
//! ## Usage
//!
//! ### Define the schema
//!
//! ```ignore
//! use structural_typing::structural;
//!
//! #[structural]
//! struct User {
//!     id: u32,
//!     name: String,
//!     email: String,
//! }
//! ```
//!
//! The `#[structural]` macro generates a module named `user` containing a `Fields` trait with
//! associated types for each field. This enables compile-time tracking of which fields are present.
//!
//! ### Generic functions with field requirements
//!
//! Functions can require specific fields through trait bounds using the generated `Fields` trait.
//! The `Presence` type can be `Present` (`T`), `Optional` (`Option<T>`), or `Absent` (`PhantomData<T>`):
//!
//! ```ignore
//! # use structural_typing::{structural, presence::Present};
//! #
//! # #[structural]
//! # struct User {
//! #     id: u32,
//! #     name: String,
//! #     email: String,
//! # }
//! #
//! // Requires both id and name
//! fn display_user<F: user::Fields<id = Present, name = Present>>(user: &User<F>) {
//!     println!("User #{}: {}", user.id, user.name);
//! }
//! ```
//!
//! Relaxing requirements is backward compatible. Existing callers with id and name continue to work
//! if we remove the `name` requirement—unlike changing a function parameter from `T` to `Option<T>`,
//! which breaks all existing call sites.
//!
//! ```ignore
//! # use structural_typing::{structural, presence::Present, access::Access};
//! #
//! # #[structural]
//! # struct User {
//! #     id: u32,
//! #     name: String,
//! #     email: String,
//! # }
//! #
//! // Requires only id; adapts behavior based on whether name is present
//! fn display_user<F: user::Fields<id = Present>>(user: &User<F>) {
//!     if let Some(name) = user.name.get() {
//!         println!("User #{}: {}", user.id, name);
//!     } else {
//!         println!("User #{}", user.id);
//!     }
//! }
//! ```
//!
//! ### Build instances incrementally
//!
//! The builder API infers field presence from the value type:
//!
//! ```ignore
//! # use structural_typing::{structural, presence::Present, access::Access};
//! #
//! # #[structural]
//! # struct User {
//! #     id: u32,
//! #     name: String,
//! #     email: String,
//! # }
//! #
//! # fn display_user<F: user::Fields<id = Present>>(user: &User<F>) {
//! #     if let Some(name) = user.name.get() {
//! #         println!("User #{}: {}", user.id, name);
//! #     } else {
//! #         println!("User #{}", user.id);
//! #     }
//! # }
//! #
//! let bob = user::empty().id(123);
//! display_user(&bob);
//!
//! let bob = bob.name("Bob".to_owned());
//! ```
//!
//! ### Serde integration
//!
//! Enable the `serde` feature to use structural types with serde.
//!
//! The `select!` macro creates concrete types, useful for serialization boundaries:
//!
//! ```ignore
//! use serde::{Deserialize, Serialize};
//!
//! #[structural]
//! #[derive(Serialize, Deserialize)]
//! struct User {
//!     id: u32,
//!     name: String,
//!     email: String,
//! }
//!
//! fn insert_user<F: user::Fields<email = Present>>(
//!     user: User<F>
//! ) -> User<select!(user: id, ..F)> {
//!     // Insert to database, get generated ID
//!     user.id(42)
//! }
//!
//! let json = r#"{"name": "Alice", "email": "alice@example.com"}"#;
//! // name optional, email present, id absent
//! let req: User<select!(user: name?, email)> = serde_json::from_str(json)?;
//!
//! let response = insert_user(req);
//! let json = serde_json::to_string(&response)?;
//! // => {"id":42, "name": "Alice", "email": "alice@example.com"}
//! ```
//!
//! ### Extract and merge
//!
//! ```ignore
//! # use structural_typing::{structural, select};
//! #
//! # #[structural]
//! # struct User {
//! #     id: u32,
//! #     name: String,
//! #     email: String,
//! # }
//! #
//! # let alice = user::empty()
//! #     .id(42)
//! #     .name("Alice".to_owned())
//! #     .email("alice@example.com".to_owned());
//! #
//! let (credentials, id_only) = alice.extract::<select!(user: name, email)>();
//! assert_eq!(credentials.name, "Alice");
//! assert_eq!(id_only.id, 42);
//!
//! let alice = credentials.merge(id_only);
//! // Merged values override existing values
//! let overridden = alice.merge(user::empty().id(21));
//! assert_eq!(overridden.name, "Alice");
//! assert_eq!(overridden.id, 21);
//! ```
//!
//! ### Nested schemas
//!
//! Schemas can contain other structural types:
//!
//! ```ignore
//! use structural_typing::{structural, presence::Present};
//!
//! #[structural]
//! struct Address {
//!     street: String,
//!     city: String,
//!     zip: String,
//! }
//!
//! #[structural]
//! struct User<A: address::Fields> {
//!     id: u32,
//!     name: String,
//!     address: Address<A>,
//! }
//!
//! // Require specific nested fields
//! fn ship<A, F>(user: User<A, F>)
//! where
//!     A: address::Fields<street = Present, city = Present>,
//!     F: user::Fields<id = Present, address = Present>
//! {
//!     println!("Shipping to {} at: {}, {}",
//!         user.id, user.address.street, user.address.city);
//! }
//! ```
//!
//! #### Nested setters
//!
//! Use `#[nested(...)]` to generate convenient setters for nested struct fields:
//!
//! ```ignore
//! use structural_typing::{structural, select};
//!
//! #[structural]
//! struct User<A: address::Fields = select!(address: all-)> {
//!     id: u32,
//!     name: String,
//!     #[nested(address: street, city, zip)]
//!     address: Address<A>,
//! }
//!
//! // Setters are generated with field_nested_field naming
//! let user = user::empty()
//!     .id(1)
//!     .name("Alice".to_owned())
//!     .address(address::empty())
//!     .address_city("Seattle".to_owned())
//!     .address_street("Main St".to_owned());
//!
//! assert_eq!(user.address.city, "Seattle");
//! assert_eq!(user.address.street, "Main St");
//! ```
//!
//! Nested setters work by extracting the nested field, updating it, and merging back—preserving all
//! other fields' presence states. This makes them compatible with `extract()` and other structural operations.
//!
//! **Limitations**:
//! - `#[nested]` requires the parent struct to have at least 2 fields because the
//!   implementation uses the spread operator, which needs other fields to preserve. Single-field parent
//!   structs will produce a compile error.
//! - Merge operations between instances with different nested field presence states are not supported.
//!   The nested struct's generic parameter must match for merge to work.
//!
//! See the [examples](https://github.com/Crazytieguy/structural-typing-rs/tree/master/examples)
//! directory for more comprehensive usage.
//!
//! ## Design
//!
//! The `#[structural]` macro generates a module containing a `Fields` trait with associated types
//! for each field. Field presence is tracked through type-level markers (`Present`, `Optional`,
//! `Absent`) that implement the `Presence` trait. Functions express requirements through trait bounds,
//! and the builder API uses type inference to determine field states.
//!
//! This approach enables:
//! - **Compile-time verification**: All field requirements checked during compilation
//! - **Zero runtime overhead**: No dynamic checks or boxing
//! - **API evolution**: Relaxing requirements is backward compatible
//! - **Flexible composition**: Merge, extract, and transform with compile-time guarantees

#![deny(missing_docs)]
#![warn(clippy::pedantic)]

/// Runtime field access trait for checking presence and getting values.
pub mod access;
/// Traits for splitting structs into selected fields and remainder.
pub mod extract;
/// Type-level presence markers and traits for field state tracking.
pub mod presence;
/// Serde integration helpers.
#[cfg(feature = "serde")]
pub mod serde;

pub use structural_typing_macros::structural;

/// Construct a `FieldSet` by selecting fields from a module.
///
/// # Presence States
///
/// | Suffix | Presence | Field Type |
/// |--------|----------|------------|
/// | (none) | Present | `T` |
/// | `?` | Optional | `Option<T>` |
/// | `-` | Absent | `PhantomData<T>` |
///
/// Access is always `user.field`. In generic code use `.get()` from the `Access` trait.
///
/// # Syntax Reference
///
/// | Pattern | Description |
/// |---------|-------------|
/// | `select!(mod: field)` | field is Present (required) |
/// | `select!(mod: field?)` | field is Optional |
/// | `select!(mod: field-)` | field is Absent |
/// | `select!(mod: field<P>)` | field has custom presence type P |
/// | `select!(mod: all)` | all fields Present |
/// | `select!(mod: all?)` | all fields Optional |
/// | `select!(mod: all-)` | all fields Absent |
/// | `select!(mod: f1, f2?)` | multiple fields (f1=Present, f2=Optional) |
/// | `select!(mod: f, ..F)` | spread: f=Present, rest inherited from F |
/// | `select!(mod: f?, ..F)` | spread: f=Optional, rest inherited from F |
/// | `select!(mod: f, all-)` | f=Present, all others Absent |
///
/// # Examples
///
/// ```ignore
/// // Concrete types for API boundaries
/// type Create = select!(user: name, email);      // Both required
/// type Update = select!(user: name?, email?);    // Both optional
///
/// // Generic: add id field to any existing fields
/// type WithId<F: user::Fields> = select!(user: id, ..F);
///
/// // Function using concrete type
/// fn create(user: User<Create>) -> User<WithId<Create>> { ... }
/// ```
#[macro_export]
macro_rules! select {
    // Error: spread without fields
    ($($module:ident)::+ : .. $spread:ty) => {
        compile_error!("select! requires at least one explicit field before spread operator")
    };

    // Error: empty field list
    ($($module:ident)::+ :) => {
        compile_error!("select! requires at least one field")
    };

    // Single field with spread: Present
    ($($module:ident)::+ : $field:ident, .. $spread:ty) => {
        $($module)::+::with::$field<::structural_typing::presence::Present, $spread>
    };

    // Single field with spread: Optional
    ($($module:ident)::+ : $field:ident ?, .. $spread:ty) => {
        $($module)::+::with::$field<::structural_typing::presence::Optional, $spread>
    };

    // Single field with spread: Absent
    ($($module:ident)::+ : $field:ident -, .. $spread:ty) => {
        $($module)::+::with::$field<::structural_typing::presence::Absent, $spread>
    };

    // Single field with spread: Custom type
    ($($module:ident)::+ : $field:ident < $presence:ty >, .. $spread:ty) => {
        $($module)::+::with::$field<$presence, $spread>
    };

    // Single field: Present
    ($($module:ident)::+ : $field:ident) => {
        $($module)::+::with::$field
    };

    // Single field: Present with trailing comma
    ($($module:ident)::+ : $field:ident,) => {
        $($module)::+::with::$field
    };

    // Single field: Optional
    ($($module:ident)::+ : $field:ident ?) => {
        $($module)::+::with::$field<::structural_typing::presence::Optional>
    };

    // Single field: Optional with trailing comma
    ($($module:ident)::+ : $field:ident ?,) => {
        $($module)::+::with::$field<::structural_typing::presence::Optional>
    };

    // Single field: Absent
    ($($module:ident)::+ : $field:ident -) => {
        $($module)::+::with::$field<::structural_typing::presence::Absent>
    };

    // Single field: Absent with trailing comma
    ($($module:ident)::+ : $field:ident -,) => {
        $($module)::+::with::$field<::structural_typing::presence::Absent>
    };

    // Single field: Custom type
    ($($module:ident)::+ : $field:ident < $presence:ty >) => {
        $($module)::+::with::$field<$presence>
    };

    // Single field: Custom type with trailing comma
    ($($module:ident)::+ : $field:ident < $presence:ty >,) => {
        $($module)::+::with::$field<$presence>
    };

    // Multiple fields: Optional + rest
    ($($module:ident)::+ : $field:ident ?, $($rest:tt)+) => {
        $($module)::+::with::$field<::structural_typing::presence::Optional, select!($($module)::+ : $($rest)+)>
    };

    // Multiple fields: Absent + rest
    ($($module:ident)::+ : $field:ident -, $($rest:tt)+) => {
        $($module)::+::with::$field<::structural_typing::presence::Absent, select!($($module)::+ : $($rest)+)>
    };

    // Multiple fields: Custom type + rest
    ($($module:ident)::+ : $field:ident < $presence:ty >, $($rest:tt)+) => {
        $($module)::+::with::$field<$presence, select!($($module)::+ : $($rest)+)>
    };

    // Multiple fields: Present + rest
    ($($module:ident)::+ : $field:ident, $($rest:tt)+) => {
        $($module)::+::with::$field<::structural_typing::presence::Present, select!($($module)::+ : $($rest)+)>
    };
}