diff options
| author | JF Bastien <jfb@chromium.org> | 2015-06-09 16:11:34 +0200 |
|---|---|---|
| committer | JF Bastien <jfb@chromium.org> | 2015-06-09 16:11:34 +0200 |
| commit | 54671fb0bd6689789cefcd26215d0bb7a42bb40c (patch) | |
| tree | 38eea8513c07b0ce30a2dd0fcbf885b07b8d57f1 | |
| parent | bfc67e8b9671bfd7b2be1f646ba40481f125538e (diff) | |
| download | nanowasm-design-54671fb0bd6689789cefcd26215d0bb7a42bb40c.tar.gz | |
Missing space.
| -rw-r--r-- | MVP.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -36,7 +36,7 @@ separate docs with more precise descriptions of: and pointer sharing. Dynamic linking would be semantically distinct from importing, though. * When compiling from C++, imports would be generated for unresolved `extern` - functions and calls to those `extern` functions would call the import. + functions and calls to those `extern` functions would call the import. * Host environments can define builtin modules that are implemented natively but can otherwise be imported like [other modules](MVP.md#Modules). As examples: * A WebAssembly shell might define a builtin `stdio` library with an export |