possibility of automating the binding generation?

did:plc:ab5inzxnpw4j2zvzlxupr5ut opened this 4d ago 3 comments
did:plc:ab5inzxnpw4j2zvzlxupr5ut opened 4d ago

first off, I want to make one thing clear:

I DON'T know if the Go ecosystem has anything good for code generation. for Zig it's the entire comptime. for Kotlin it's KSP preprocessors and/or compiler plugins + KotlinPoet for type-safe bindings generation.

that being said, there are projects much larger than Ghostty in scale that save a lot of time thanks to programmatic code generation, such as windows and windows-sys Rust crates being nearly fully auto-generated through Microsoft's definition language used all around Windows COM.

if Zig-based libghostty-vt is already C-compatible, what stops one from generating such bindings from a known interface definition language, that being C headers?

you kinda do this with an agent skill, but spending tokens on something that could have been a build script?...

No activity yet.

cospan · schematic version control on atproto built on AT Protocol