From f0dab1b091c807aa834a72099fc557d779615577 Mon Sep 17 00:00:00 2001 From: Luke Wagner Date: Fri, 17 Jan 2025 10:30:08 -0600 Subject: [PATCH] Improve description Co-authored-by: Joel Dice --- design/mvp/Explainer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/design/mvp/Explainer.md b/design/mvp/Explainer.md index 48fb7587..b14ab1b8 100644 --- a/design/mvp/Explainer.md +++ b/design/mvp/Explainer.md @@ -738,7 +738,7 @@ variant-case payloads and function results, when `T` is absent, the "value(s)" being asynchronously passed can be thought of as [unit] values. In such cases, there is no representation of the value in Core WebAssembly (pointers into linear memory are ignored) however the *timing* of completed reads and writes -is observable and meaningful. Thus, empty futures and streams can be useful for +and the number of elements they contain are observable and meaningful. Thus, empty futures and streams can be useful for timing-related APIs. Currently, validation rejects `(stream T)` and `(future T)` when `T`