Use go.bytecodealliance.org/cmd/wit-bindgen-go to generate go bindings given WIT interfaces

[Mossaka]

Hey there, I just want to throw an idea here and see if you like it.

wit-bindgen 0.8.0 release has the newest WIT syntax that comes with a go-bindgen, which I've contributed to. In addition, it seems to me that preview2 WIT interfaces in Spin are also updated to the newest syntax. It feels nautral to me that we should be starting using wit-bindgen-go to generate go bindings and then build a go SDK on top of them. It reduces maintainence cost, and reduces the time to write the bindings manually. The benefit of a SDk is that this could go completely transparent to the users of the Spin Go SDKs.

Does this sound like a good idea?

Disclaimer: I am the author of wit-bindgen-go crate in wit-bindgen

Update

https://pkg.go.dev/go.bytecodealliance.org has the new wit-bindgen-go that can generate idiomatic Go bindings without relying on Cgo. This is the one we should use for the Go SDK.

[rylev]

I think we'd definitely be in favor of that. We need to make sure that switching to wit-bindgen 0.8 is in working order which is being done in spinframework/spin#1599. I'll try to move the Go SDK over to using the Go support in wit-bindgen in that branch.

[Mossaka]

That's great to hear, @rylev ! Let me know if you ran into any issues with the generated bindings and feel free to raise issues to the wit-bindgen repo.

[rajatjindal]

I think this issue can be closed now in favor of using wasm-tools-go

[Mossaka]

I am going to rename this issue to use go.bytecodealliance.org/cm and go.bytecodealliance.org/cmd/wit-bindgen-go to implement the Go SDK