Closed sbc100 closed 2 months ago
@dschuff @ashleynh
cc https://github.com/WebAssembly/memory64/issues/6 which has some, albeit not a whole lot more, discussion
cc #6 which has some, albeit not a whole lot more, discussion
What solution do your propose we go with memory.copy
? (1) or (2) or something else?
Actually lets just close this in favor of #6.
The memory64 proposal so far has not needed to deal with this issue since there was no multi-memory support. Now that multi-memory is at stage 4 and not that we are adding table64 support we need to decide what do about these cross-tables / cross-memory copies.
I seem like there are are basically two choices:
Supporting this would certainly blow the up the number of tests we would need to write, but thats not really a great reason not to do it. Do folks have any good reasons why we would wand to support this?