You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dimensions come from the config struct, but it looks like it might not be set up properly. Since the Load function doesn't set the dimensions, and user can forget to do that explicitly.
One solution might be to set dimensions in Load function.
Or better to add support for metadata loading in C interface, as it is done for Python.
Can you contribute to the implementation?
I can contribute
Is your feature request specific to a certain interface?
Other bindings
Contact Details
No response
Is there an existing issue for this?
I have searched the existing issues
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Describe what you are looking for
Hey, I found an unobvious behaviour with the Go code related to the index pointer and configuration. Here's what's going on:
In the Load function only the index pointer is set up, but the configuration is left with incorrect dimensions.
usearch/golang/lib.go
Lines 341 to 356 in e686a3d
In the Get function, a vector is created with a length based on dimensions from config.
usearch/golang/lib.go
Line 289 in e686a3d
Same in the Search function
usearch/golang/lib.go
Line 306 in e686a3d
The dimensions come from the config struct, but it looks like it might not be set up properly. Since the Load function doesn't set the dimensions, and user can forget to do that explicitly.
One solution might be to set dimensions in Load function.
Or better to add support for metadata loading in C interface, as it is done for Python.
Can you contribute to the implementation?
Is your feature request specific to a certain interface?
Other bindings
Contact Details
No response
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: