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
{{ message }}
Repository navigation
Include types, tables, labels, globals, and memories in binary format name section #750
I realize the name section is probably seen as a stopgap for a more expressive metadata section, but it would be nice if it could round trip the names that are in the text format. At a glance, it's missing names for imports, types, tables, and labels.
And as a minor nit, there are no distinct names for imports; imports are imported into their respective entities' index spaces, such as the function index space, so for example the existing "name" section covers imported functions.
So to summarize, the wasm binary format currently doesn't have names for:
changed the title [-]Include imports, types, tables, and labels in binary format name section[/-][+]Include types, tables, labels, globals, and memories in binary format name section[/+]on Jan 31, 2017
Activity
sunfishcode commentedon Jan 31, 2017
It's also missing names for globals and memories.
And as a minor nit, there are no distinct names for imports; imports are imported into their respective entities' index spaces, such as the function index space, so for example the existing "name" section covers imported functions.
So to summarize, the wasm binary format currently doesn't have names for:
[-]Include imports, types, tables, and labels in binary format name section[/-][+]Include types, tables, labels, globals, and memories in binary format name section[/+]jfbastien commentedon May 11, 2017
@AndrewScheidecker could you file a PR for this?
AndrewScheidecker commentedon May 15, 2017
Will do.
nomeata commentedon Jan 7, 2020
JFTR, this seems to have evolved into a proposal at https://github.com/WebAssembly/extended-name-section
binji commentedon Jan 14, 2020
Thanks for that info @nomeata! Let's close this issue then.