diff options
| author | Joseph Richey <joerichey@google.com> | 2017-11-15 08:48:14 -0800 |
|---|---|---|
| committer | JF Bastien <github@jfbastien.com> | 2017-11-15 09:48:14 -0700 |
| commit | e2be77eaac770268a4c22fb09c6f648de7b9b6b8 (patch) | |
| tree | ba99bc504cd96f6471147582e08a5e19ebd8312d /Modules.md | |
| parent | 71c97d9081ac6d64497d586e8f45c8145ed3f86e (diff) | |
| download | nanowasm-design-e2be77eaac770268a4c22fb09c6f648de7b9b6b8.tar.gz | |
Fixup links to future features (#1157)
This link standardizes how all the other design pages will refer to
future features (either in `FutureFeatures.md` or in a tracking issue).
All links to these upcoming features now use references at the bottom of
the doc page (as opposed to inline links or references).
Note that this change makes it very easy for the doc links to be updated
when a tracking issue is started. As all the references have a standard
format; a simple find/replace script will get everything.
This commit also makes sure that references now point to a tracking
issue if one exists. Note that this means a future CL can now delete
some of the unnecessary sections from `FutureFeatures.md`.
The only visible change from this commit is that certain broken links
are now fixed, or links pointing to a doc section now point to the
correct tracking issue.
Diffstat (limited to 'Modules.md')
| -rw-r--r-- | Modules.md | 5 |
1 files changed, 2 insertions, 3 deletions
@@ -6,7 +6,7 @@ with a set of import values to produce an **instance**, which is an immutable tuple referencing all the state accessible to the running module. Multiple module instances can access the same shared state which is the basis for [dynamic linking](DynamicLinking.md) in WebAssembly. WebAssembly modules -are also meant to integrate with ES6 modules in the [future :unicorn:][future ES6 modules]. +are also meant to integrate with ES6 modules in the [future :unicorn:][future modules]. A module contains the following sections: @@ -327,8 +327,7 @@ to the following nullary operators: In the future, operators like `i32.add` could be added to allow more expressive `base + offset` load-time calculations. -[future ES6 modules]: FutureFeatures.md#tracking-issues +[future modules]: https://github.com/WebAssembly/design/issues/1087 [future types]: FutureFeatures.md#more-table-operators-and-types -[future dom]: FutureFeatures.md#gc/dom-integration [future multiple tables]: FutureFeatures.md#multiple-tables-and-memories [valid UTF-8]: https://encoding.spec.whatwg.org/#utf-8-decode-without-bom-or-fail |
