Skip to content

Commit 9a7a081

Browse files
Update design/mvp/Explainer.md
Co-authored-by: Luke Wagner <mail@lukewagner.name>
1 parent c837496 commit 9a7a081

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

design/mvp/Explainer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1899,8 +1899,8 @@ In the Canonical ABI, the `{readable,writable}-future-end` is passed as an
18991899
`i32` describing the linear memory offset of the
19001900
`{readable,writable}-buffer<T; 1>`. The `option<future-{read,write}-result>`
19011901
return value is bit-packed into the single `i32` return value where
1902-
`0xffff_ffff` represents `none`. And, `future-read-result.canceled` is encoded
1903-
as the value of `future-write-result.canceled`, rather than the value implied
1902+
`0xffff_ffff` represents `none`. And, `future-read-result.cancelled` is encoded
1903+
as the value of `future-write-result.cancelled`, rather than the value implied
19041904
by the `enum` definition above.
19051905

19061906
(See [`canon_future_read`] in the Canonical ABI explainer for details.)

0 commit comments

Comments
 (0)