Jordan Last

@kingrial I'm sorry for our loss, this is kind of tragic

Sweet, I might take you up on that

You might want to hold off on the exports and go straight to ES modules, which will be standard across all JS VMs. This will be much better than using...

I imagine compiling to wasm might fix this and all other gc issues, since the wasm VM doesn't even support GC yet.

And wasm has it's own VM designed for non-GC languages like C/C++, so your compiled code isn't running in a GC VM at all once compiled to wasm.

> i128, on the other hand, cannot be converted to JavaScript the same way as Rust uses it. Either it gets converted to f64, and therefore loses precision, or it...

> It might make sense to add From conversions to JsBigInt, to make this easier, but not for JsValue. In any case, I don't think Boa should force anything on...

To sum up, using `i128` as an example, I agree that we should allow the developer to convert to a JS `Number` or `BigInt` at will. But I believe that...

To add to this, going the other way would also be really nice. I would like to be able to convert values of arbitrary Rust types into `JsValue`s, and that...

Having this API implemented would solve a host of issues for my project: https://github.com/demergent-labs/azle/issues/142 I am ready to start working on this as soon as tomorrow, it's a major blocking...