Designing a narrow C ABI for BlazeDB, a Swift-native storage engine

BlazeDB’s Swift API is typed, KeyPath-friendly, and intentionally Swift-shaped. Its C API currently has six functions. That gap is deliberate. I did not set out to port the Swift API into C. I wanted the smallest useful boundary through which another runtime could use the same storage engine without turning Swift’s type system, query DSL, or object layouts into a permanent interoperability contract. The question that kept coming back was simple: where should Swift stop? Repo: https://github.co...