I'm curious if you'd be open to changing the API to return idiomatic Go errors instead of idiomatic C codes. In other words, this would replace Return with error in all of the Go-friendly wrappers.
It would be a breaking change and would be a hassle for existing users, but it would be much more ergonomic for new users.
I'm curious if you'd be open to changing the API to return idiomatic Go errors instead of idiomatic C codes. In other words, this would replace
Returnwitherrorin all of the Go-friendly wrappers.It would be a breaking change and would be a hassle for existing users, but it would be much more ergonomic for new users.