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
A syminfo currently identifies its symbol by name. It seems like it would be simpler, more consistent with wasm encoding in general, and consistent with the ELF-like principle of not referring to symbols within the same module by name, and possibly faster to link, if it identified symbols by index.
It would also work well with #29, in case it became important to add symbol flags to local symbols, because local symbols have indices.
It would need some way to indicate the type of index: function, global, table, or memory. I expect we could either split WASM_SYMBOL_INFO into 4 codes, WASM_FUNCTION_SYMBOL_INFO and so on, or we could add external_kind bytes.
The text was updated successfully, but these errors were encountered:
A
syminfo
currently identifies its symbol by name. It seems like it would be simpler, more consistent with wasm encoding in general, and consistent with the ELF-like principle of not referring to symbols within the same module by name, and possibly faster to link, if it identified symbols by index.It would also work well with #29, in case it became important to add symbol flags to local symbols, because local symbols have indices.
It would need some way to indicate the type of index: function, global, table, or memory. I expect we could either split
WASM_SYMBOL_INFO
into 4 codes,WASM_FUNCTION_SYMBOL_INFO
and so on, or we could addexternal_kind
bytes.The text was updated successfully, but these errors were encountered: