Great talk. To be clear, this is a bootstrap of C code into C-code-in-Go, which will be followed by idiomatic Go work.
That sounds interesting — what kinds of changes do you think will be needed to make it idiomatic Go? Are there places where tagged unions should be replaced with interfaces, for example?
Return codes would be the obvious example to me. Go prefers two return values instead of overloading a single return.
Great talk. To be clear, this is a bootstrap of C code into C-code-in-Go, which will be followed by idiomatic Go work.
That sounds interesting — what kinds of changes do you think will be needed to make it idiomatic Go? Are there places where tagged unions should be replaced with interfaces, for example?
Return codes would be the obvious example to me. Go prefers two return values instead of overloading a single return.