-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JS API changes? #24
Labels
Comments
Not familiar with the JS API design myself.. @backes did you run into this? |
I didn't hit this yet, but the V8 implementation is not complete yet. Also, we currently still only allow up to 4GB memories, even if you use 64 bit for indexing. But I agree that the JS API will need changes. |
@lars-t-hansen what do you propose for the value of "index"? The string |
SpiderMonkey currently uses “i32” and “i64” for the JS-type representation of index type. IIRC, that’s what the memory64 proposal uses in the text format, so we were trying to stay symmetrical to that.
… On Aug 19, 2022, at 9:16 AM, Sam Clegg ***@***.***> wrote:
@lars-t-hansen what do you propose for the value of "index"? The string u64 or u32 maybe?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
I believe this is fixed by #39 |
sbc100
pushed a commit
that referenced
this issue
Jun 12, 2024
backes
pushed a commit
to backes/wasm-spec-memory64
that referenced
this issue
Oct 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This proposal looks like it might need changes to the JS API, off the top of my head at least these:
The text was updated successfully, but these errors were encountered: