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
e.ext.ai.search(e.SomeIndexedType,newFloat32Array([0.0]));// or with params, which type checks but does not work at query-build-timee.params({searchTerm: e.array(e.float32)},(params)=>e.ext.ai.search(e.SomeIndexedType,params.searchTerm));
Error or desired behavior
No function overload found for 'e.ext.ai.search()' with args: Element: default::Post (Many), Element: arraystd::float32 (One)
Digging in here, it seems that in our functionality that compares the argument type to the function type definition, we end up casting the std::float32 to std::number and then comparing against std::float32 (which is false), and we are not generating an implicit cast map entry between std::float32 and std::number so that comparison is also returning false.
Versions (please complete the following information):
EdgeDB version (e.g. 2.0): 5.3
EdgeDB CLI version (e.g. 2.0): 5.2.0
edgedb-js version (e.g. 0.20.10;): 1.5.7
@edgedb/generate version (e.g. 0.0.7;): 0.5.3
The text was updated successfully, but these errors were encountered:
Code
Error or desired behavior
Digging in here, it seems that in our functionality that compares the argument type to the function type definition, we end up casting the
std::float32
tostd::number
and then comparing againststd::float32
(which is false), and we are not generating an implicit cast map entry betweenstd::float32
andstd::number
so that comparison is also returning false.Versions (please complete the following information):
2.0
): 5.32.0
): 5.2.0edgedb-js
version (e.g.0.20.10
;): 1.5.7@edgedb/generate
version (e.g.0.0.7
;): 0.5.3The text was updated successfully, but these errors were encountered: