Skip to content

Commit 19c1fc6

Browse files
committed
Remove stale text in Async.md regarding error-context
1 parent 3dacde1 commit 19c1fc6

1 file changed

Lines changed: 2 additions & 5 deletions

File tree

design/mvp/Async.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -369,11 +369,8 @@ example, given `f` and `g` with types:
369369
f: func(x: whatever) -> stream<T>;
370370
g: func(s: stream<T>) -> stuff;
371371
```
372-
`g(f(x))` works as you might hope, concurrently streaming `x` into `f` which
373-
concurrently streams its results into `g`. If `f` has an error, it can close
374-
its returned `stream<T>` with an [`error-context`](Explainer.md#error-context-type)
375-
value which `g` will receive along with the notification that its readable
376-
stream was closed.
372+
Given this, `g(f(x))` works as you might hope, concurrently streaming the
373+
results of `f` into `g`.
377374

378375
Given the readable or writable end of a stream, core wasm code can call the
379376
imported `stream.read` or `stream.write` canonical built-ins, resp., passing the

0 commit comments

Comments
 (0)