aboutsummaryrefslogtreecommitdiff
path: root/EssentialPostMVPFeatures.md
diff options
context:
space:
mode:
authorJF Bastien <jfb@chromium.org>2015-06-11 17:20:31 +0200
committerJF Bastien <jfb@chromium.org>2015-06-11 17:20:31 +0200
commit83bbf1108534eb8ea8e6fa66122d5cad616b9c38 (patch)
treef3a75a0565d773e585cc751e0c4ebb7d6aa6a5d5 /EssentialPostMVPFeatures.md
parentd6845563e73f6e6eccf3398d5fc38a56ad4dbf67 (diff)
downloadnanowasm-design-83bbf1108534eb8ea8e6fa66122d5cad616b9c38.tar.gz
Be more formal.
Diffstat (limited to 'EssentialPostMVPFeatures.md')
-rw-r--r--EssentialPostMVPFeatures.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/EssentialPostMVPFeatures.md b/EssentialPostMVPFeatures.md
index c2439a9..2727f92 100644
--- a/EssentialPostMVPFeatures.md
+++ b/EssentialPostMVPFeatures.md
@@ -46,8 +46,8 @@ The WebAssembly MVP will support two no-exception modes for C++:
These modes are very unfortunate for code bases which rely on C++ exception
handling, but are perfectly acceptable for C code, or for C++ code which avoids
-exceptions. This doesn't prevent developers from using the STL… as long as their
-code doesn't encounter exceptional cases!
+exceptions. This doesn't prevent developers from using the STL: their code will
+function correctly as long as it doesn't encounter exceptional cases.
Post-MVP, WebAssembly will gain support for developer access to stack unwinding,
inspection, and limited manipulation. These are critical to supporting zero-cost