Skip to content

Commit 1903981

Browse files
committed
Link to post-MVP future
1 parent 9a813cd commit 1903981

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

_posts/2018-10-24-multithreading-rust-and-wasm.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@ When WebAssembly was first shipped it was an [MVP] which, while minimal, has
88
spawned a huge number of exciting projects which work today across all major
99
browsers. Rust has capitalized on the wasm MVP's success as well with tools
1010
like [`wasm-bindgen`] and [`wasm-pack`] by making the MVP feel less minimal.
11-
WebAssembly is yet more ambitious, though! Since inception it's always been
12-
intended to extend the [WebAssembly specification][spec] with new features and
13-
functionality.
11+
WebAssembly is [yet more ambitious][post-mvp], though! Since inception it's
12+
always been intended to extend the [WebAssembly specification][spec] with new
13+
features and functionality.
1414

1515
One of the features I'm particularly excited about coming down the pike for
1616
WebAssembly is the [threads] proposal. The threading proposal was unfortunately
@@ -643,3 +643,4 @@ Discord](https://discord.gg/6SHrCn), or follow along on GitHub with either
643643
[procedural macro]: https://doc.rust-lang.org/nightly/reference/procedural-macros.html
644644
[`wasm-opt`]: https://github.com/webassembly/binaryen
645645
[`Atomics.waitAsync`]: https://github.com/tc39/proposal-atomics-wait-async
646+
[post-mvp]: https://hacks.mozilla.org/2018/10/webassemblys-post-mvp-future/

0 commit comments

Comments
 (0)