From 93e4e3b2d27884bf0cc989bed4f1161074804ada Mon Sep 17 00:00:00 2001 From: Brad Nelson Date: Thu, 27 Oct 2016 20:58:36 -0700 Subject: Tagging future features with icon. (#839) Added brief item on multiple return. --- FutureFeatures.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'FutureFeatures.md') diff --git a/FutureFeatures.md b/FutureFeatures.md index 69bbcf5..795437d 100644 --- a/FutureFeatures.md +++ b/FutureFeatures.md @@ -2,7 +2,8 @@ These are features that make sense in the context of the [high-level goals](HighLevelGoals.md) of WebAssembly but are not considered part -of the [Minimum Viable Product](MVP.md) or the essential [post-MVP](PostMVP.md) +of the [Minimum Viable Product](MVP.md) or the essential +[post-MVP :unicorn:](PostMVP.md) feature set which are expected to be standardized immediately after the MVP. These will be prioritized based on developer feedback, and will be available under [feature tests](FeatureTest.md). @@ -420,6 +421,11 @@ of WebAssembly in browsers: custom compression (on top of the spec-defined binary format, under generic HTTP `Content-Encoding` compression). +## Multiple Return + +The stack based nature of WebAssembly lends itself to the possibility +of supporting multiple return values from blocks / functions. + ## Multiple Tables and Memories The MVP limits modules to at most one memory and at most one table (the default -- cgit v1.2.3