WebAssembly/module-linking
Proposal for allowing modules to define, import and export modules and instances
WebAssemblyNOASSERTION
Issues
- 3
- 2
- 6
- 4
- 2
Unclear how text format uses type index
#45 opened by Pyrolistical - 3
Do we care about polyfillibility?
#42 opened by Pyrolistical - 4
Library on demand (LOD) in WASI
#38 opened by vasuskimo - 5
- 6
Introduce arbitrary import/export depth
#29 opened - 2
- 3
- 1
- 28
- 11
- 11
Module types need their own index spaces
#21 opened by rossberg - 10
how about dlopen
#33 opened by lum1n0us - 3
- 5
Intermingled import/type sections and elaboration to single-level instance imports
#17 opened by alexcrichton - 2
- 4
Nested parent aliases
#20 opened by rossberg - 19
Alias shorthand syntax
#19 opened by rossberg - 4
Should engines validate the number of instances created by module-linking modules?
#27 opened by alexcrichton - 3
Aliasing outer imported modules forces modules to have per-instance runtime state
#28 opened by alexcrichton - 6
- 2
- 6
- 5
- 11
Very Future Thinking: Module Linking Relationship with Conditional Sections and Registry Enviornments
#10 opened by torch2424 - 12
- 2
References to modules/instances?
#4 opened by lachlansneff - 4
Need some way to declare thrown exceptions?
#2 opened by tlively