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
for context: memory.init (already) needs to know the data segment length so it can trap, but trapping isn't particularly useful for programs. a data.length would expose the length in an useful way (non-trapping).
a hypothetical single-pass compiler could use a data.length opcode for generated data segments, since data segments come after code segments. such data.length opcode also happens to be oddly convenient when hand-writing wasm/wat.
we should have data.length opcode
(it should return 0 for dropped segments ofc)
The text was updated successfully, but these errors were encountered: