Optimize client crate development using FFI

[BirnadinErick]

Wouldn't it be nice to have a single client library written in rust and then use FFI to use them in other programming languages like C and go? I was just 🤔!

How (a vague idea)

Write the library in rust, then build platform specific shared object like .so for *nix & .dll for Windows.
Or some other way? Rust already has docs to do it with C itself, docs, using FFI. Hope go would have same feature too.

Advantages

1. Less client libraries to manage
2. Less code to develop, maintain during changes to SurrealDB APIs
3. Better to use rust's Borrow checker than own mem-management in C or go's garbage collector (I think this is better for performance? idk)
4. Efficient workflow (just an opinion)

Disadvantages

1. Lose functionality found in C or go like raw-pointers
2. Requires a mechanism to pass data from rust-lib to caller

[BirnadinErick]

For caller-callee mechanism how about do everything in rust side the usual way and return the result in string (JSON-format) and parse it in caller (C or go) side?

Or may a struct like this?

struct SurealResponse {
    time: f32,
    result: serde::Value | &str,
    status: bool,
}

And rust would communicate with SUrrealDB using websockets?