diff options
| author | JF Bastien <github@jfbastien.com> | 2016-12-29 13:50:00 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-12-29 13:50:00 -0800 |
| commit | a9ccc82e2ab9db3af1acb30ec70cda82e1f30803 (patch) | |
| tree | 5e3059bf0d64e754c949cb5f3f0a3d2505a18dfd | |
| parent | 1183d87891aa52c632b84b56a6f58482324af1fa (diff) | |
| download | nanowasm-design-a9ccc82e2ab9db3af1acb30ec70cda82e1f30803.tar.gz | |
Export name uniqueness (#932)
* Export name uniqueness
spec test exports.wast makes it a validation failure for exported names to be duplicate. I find this somewhat surprising (I see exports as a dictionary, so duplicates simply overwrite previous entries), I'd therefore be happy if others want to reverse the polarity of this (make it OK to duplicate export names).
* Fix unintended change
| -rw-r--r-- | Modules.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -118,6 +118,8 @@ if another WebAssembly instance imports the definition, then both instances will share the same definition and the associated state (global variable value, linear memory bytes, table elements) is shared. +Export names must be unique. + In the MVP, only *immutable* global variables can be exported. ## Integration with ES6 modules |