it would be nice to support f32, f64 in index(btree) as it is the base for vectors and basically used everywhere in games.
i understand that there will always be a EPSILON uncertainty but i can live with that. the advantage of not having to store the position as i32, i64 and convert + div 1000 to get the position is more than worth the edge cases on the edge (pun intended).
i would even be fine if the index floats just get rounded to 0.01 precision and converted to i32/i64 (with * 100) to act as easy to compare value.
Requested by @xDovos via the SpacetimeDB site.
it would be nice to support f32, f64 in index(btree) as it is the base for vectors and basically used everywhere in games.
i understand that there will always be a EPSILON uncertainty but i can live with that. the advantage of not having to store the position as i32, i64 and convert + div 1000 to get the position is more than worth the edge cases on the edge (pun intended).
i would even be fine if the index floats just get rounded to 0.01 precision and converted to i32/i64 (with * 100) to act as easy to compare value.
Requested by @xDovos via the SpacetimeDB site.