Why reimplement zvec in Go instead of using the zvec Go bindings?

Hi, I’m one of the core developers of zvec. I recently came across the xvec project on GitHub and was curious about the motivation behind reimplementing zvec in Go rather than using the existing zvec Go bindings.

What limitations or disadvantages did you encounter when using the zvec Go bindings in Gorse?

Thank you for your time and insights!

The issue asks for the motivation behind xvec reimplementing zvec in Go instead of using zvec's Go bindings, but names no files, tests, or entry points. Start by reviewing the repository context and existing discussion; done means documenting a maintainer-confirmed explanation of the bindings' limitations or disadvantages.

Written by the indexing model from the issue text.