Wasm arrays as arguments and return types #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
This PR adds the following:
JsValue
into a rust struct that is wasm binded (required for the below 2 array ops)Related
wasm-bindgen
issues:The problem with using JSON /
serde
for handling passing/receiving arrays is that deser/ser converts to JS objects instead of classes so library consumers can't use class methods without converting to or from JSON first. With the derives added in this PR this is no longer neededSimple example not using arrays but to describe the problem with JSON:
Rust
JS
The hope is one day
wasm_bindgen
supports vecs of structs so we can remove this 😄