Map JS Types to Rust - Githubissues

yoshuawuyts commented 6 years ago

Currently we only support passing i32 integers — great for math, but having more options would be great! We should probably look into rust-experiments and add some of the things they're doing.

Also s/o to @killercup for giving pointers to get in the right direction! 🙏

Complex JS types

Things like Objects, and the other higher-order JS things might need to be mapped down to strings before they can be passed (or, like json). There's been talk of using protobufs, but it seems most people are rather "meh" about it.

Mapping strings

Mapping utf16 to utf8 can either be done in Rust or in JS. I'm not sure about the Rust version, but the JS version seems to be:

Browser

var encode = (new TextEncoder('utf-8')).encode
console.log(encode('hello world')
// => [Uint8Array]

var decode = (new TextDecoder('utf-8')).decode
console.log(decode(SomeUint8Array)
// =>'hello world'

Node

var TextEncoder = require('util').TextEncoder
var TextDecoder = require('util').TextDecoder

var encode = (new TextEncoder('utf-8')).encode
console.log(encode('hello world')
// => [Uint8Array]

var decode = (new TextDecoder('utf-8')).decode
console.log(decode(SomeUint8Array)
// =>'hello world'

Rust

This should also be possible from within Rust, as the code is rather fast (and small) thanks to optimizations. There's a possibility of creating custom attributes such as #[expose_wasm] to help streamline mappings in Rust, but it seems to rely on experimental Nightly features and nobody seems to have tried it yet.

Shared memory

Now in an ideal scenario, we could use SharedArrayBuffers to allocate memory in JS, and then pass it to Rust. I'm not sure if this is feasible, but it'd be neat if it were the case.