Skip to content

RFCs (Design records)

RFCs are design/evolution records (PEP-style). They are primarily for contributors and advanced readers.

  • RFCs are not canonical user docs.
  • User docs may link to RFCs for background and rationale.

For status, see: Roadmap.

Index

Tip: press Esc to clear.

RFC Status Track Title
RFC 000 Done closed / implemented Incan Core Language RFC (Phase 1)
RFC 001 Superseded closed / superseded Test Fixtures
RFC 002 Superseded closed / superseded Parametrized Tests
RFC 003 Blocked proposed / active Frontend & WebAssembly Support
RFC 004 Draft proposed / active Async Fixtures
RFC 005 Draft proposed / active Rust Interop
RFC 006 Planned proposed / active Python-Style Generators
RFC 007 Superseded closed / superseded Inline Tests
RFC 008 Done closed / implemented Const Bindings
RFC 009 Planned proposed / active Sized Integer Types & Builtin Type Registry
RFC 010 Draft proposed / active Temporary Files and Directories
RFC 011 Planned proposed / active Precise Error Spans in F-Strings
RFC 012 Draft proposed / active JsonValue Type for Dynamic JSON
RFC 013 Draft proposed / active Rust Crate Dependencies
RFC 014 Draft proposed / active Error Handling in Generated Rust Code
RFC 015 Planned proposed / active Hatch-like Tooling (Project Lifecycle CLI)
RFC 016 Planned proposed / active loop and break <value> (Loop Expressions)
RFC 017 Planned proposed / active Validated newtypes with implicit coercion (pydantic-like feel)
RFC 018 Draft proposed / active Language Primitives for Testing
RFC 019 Draft proposed / active Test Runner, CLI, and Ecosystem

See also