Raise Web implementation limits for imports and exports

[tlively]

At the CG meeting today (July 16, 2024), we had unanimous consensus to raise the limits on the number of imports and exports on the Web to 1,000,000. See WebAssembly/design#1520 for context.

[tlively]

Implementation status for this change:

• V8 (cc @jakobkummerow)
• SpiderMonkey (cc @eqrion)
• JSC (cc @ddegazio)

[eqrion]

SpiderMonkey bug which should make it into Fx130.

[rossberg]

Looks good to me, but should we hold off landing this on main until the candidate recommendation release process for 2.0 is through? We probably ought to not add any feature changes while it is under public "review".

[conrad-watt]

LGTM.

WRT questions about the W3C cut - is there not still a distinction between the WG living standard, which is (currently) subject to the review period and needs to be explicitly snapshotted, and the CG living "draft" standard? I would have thought we could still freely update the CG draft standard without interfering with the WG's review period.

see WG guidelines here
https://sideshowbarker.github.io/w3c-faq/#how-can-i-make-a-living-standard-from-my-spec

and CG guidelines here
https://sideshowbarker.github.io/w3c-faq/#cg-living-standards

[rossberg]

I am not sure. Technically, we haven't reached the W3's living standard status yet, only after we're through with the current process (hopefully very soon). And CI currently pushes every commit to W3C TR immediately. There are no two versions or places in the current setup. My understanding is that the current URL we push to is going to become the place for the living standard CR as well, in which case this setup makes sense and is not worth changing anymore. But IIUC it also means that we have to be careful not to merge functional changes right now. But I may be wrong.

[conrad-watt]

Is the public "review" mentioned above the same thing as the "exclusion opportunity" triggered by new CRs? Interpreting the above FAQ, new pushes to W3C TR don't trigger new exclusion opportunities unless we explicitly tag the push as a snapshot. Am I understanding correctly that we're currently in the 60 exclusion opportunity period for the "2.0 snapshot"?