Shu-yu Guo

> Is that true with wasm memory64? As I mentioned above, with a 64-bit wasm memory you are allowed to ask for a maximum of 2^48 pages, which is 2^64...

#1863 is interesting. Indeed the concepts of syntactic limit vs runtime limits is a good summary of the divergence. My preference is for all the JS embedding limits be syntactic...

I don't think `maxByteLength` is important enough to resolve #1863 one way or another. My revised proposal is: - "Lie" in the `maxByteLength` getter - For memory64, overflow to `Infinity`...

> As for the memory64 issue, what if as a short term stop gap to https://github.com/WebAssembly/spec/issues/1863 we agreed to a guaranteed syntactic limit for memory max of at most MAX_SAFE_INTEGER...

> As for the memory64 issue, what if as a short term stop gap to https://github.com/WebAssembly/spec/issues/1863 we agreed to a guaranteed syntactic limit for memory max of at most MAX_SAFE_INTEGER...

what the hell

Is the fix equivalent to another lookahead checking for `=` or `;`? Edit: Oh I guess just `=` because it's a const.

STR is pretty commonly used in implementations' issue trackers, but I also feel like it doesn't come up for committee.

Editor call: | Function | Make optional parameters required? | |--|--| | `Object ( [ value ] )` | Yes | | `Object.assign ( target, ...sources )` | No |...

Sorry I don't actually remember discussing serialization of Temporal objects. At this time I can't reconstruct any reasons why V8 would be against it.