You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
error: failed to generate a standard wasm bindings custom section
caused by: failed to map return value for export `render` to standard binding expressions
caused by: cannot represent 64-bit integer with a standard bindings expression
Expected behavior:
it should correctly generate interface type for the return value
In the proposal the types from u8/s8 to u64/s64 are covered, where u stands for unsigned and s for signed.
Thanks for the report! This is definitely something that I think we should support better in wasm-bindgen and is sort of "legacy baggage" from the JS target. I've opened up #1841 which is sort of the extension of this issue about how "pure interface types" isn't super well supported today since all the web functionality is mixed in. This would be fixed as part of a split proposed there.
Consider the following code
Compiling it with
produces
Expected behavior:
it should correctly generate interface type for the return value
In the proposal the types from u8/s8 to u64/s64 are covered, where
u
stands for unsigned ands
for signed.wasm-pack 0.8.1
wasm-bindgen 0.2.52
rustc 1.38.0 (625451e37 2019-09-23)
The text was updated successfully, but these errors were encountered: