Design decisions, language proposals, and updates from the Kairo team and community contributors.
Full transparency on where and how AI tooling is used across the Kairo project.
The design reasoning behind replacing switch with match as Kairo's multi-way dispatch construct.
Why Kairo has one pointer type instead of splitting pointers and references, and how AMT makes it work without runtime cost.
The design reasoning behind Kairo's native C++ interoperability and why we skipped the binding generator approach entirely.
