Rust and Go implementations

[davebryson]

For anyone interested, Go and Rust implementations are in the works here:
Rust version . (primary focus)
Go version

Goal is to provide both a file based store and a key/value store as an alternative

[chjj]

Wow, totally awesome! Now we just need a C implementation and we have all the bases covered. :)

[chjj]

I noticed you added flags as a member of the node struct in the rust impl. That flags field probably isn't as necessary for rust. In node.js it's just meant to keep heat off of the javascript GC (having one field packed into bits is smaller than having multiple properties on the object). Rust probably has the luxury of making things a lot cleaner since it has no GC overhead.

[adrianbrink]

It is possible to export a C api from the Rust implementation. That way we don't have to maintain an extra implementation. Even for other languages we can simply write thin wrappers around the C implementation.

Rust FFI
Rust FFI Examples

[davebryson]

I noticed you added flags as a member of the node struct in the rust impl. That flags field probably isn't as necessary for rust.

Ahhh, ok. I need to work through that a bit more. I actually have some uncommitted refactoring and updates I'll add that to.

[davebryson]

It is possible to export a C api from the Rust implementation. That way we don't have to maintain an extra implementation. Even for other languages we can simply write thin wrappers around the C implementation.

Haven't really thought about that much. Am trying to see how far I can get with a "safe" implementation.

[adrianbrink]

Exposing methods to C is still safe. It only means that the Rust compiler does the memory layout in a way which is compatible with C. This is arguably the best part of the Rust FFI. It allows you to gradually replace old unsafe C code with safe Rust code.

[davebryson]

@chjj Regarding flags, I can't seem to find any where in the code base where the setter node.leaf = ... is actually used. It appears flag values come solely from the node.pos setter, is that correct? Part of my confusion here is probably coming from me trying to grok the low level storage layout/format

[davebryson]

In case there's any interest, the latest Rust version now has the initial file store working:
ukel-trie. Not complete, but getting there.