Skip to content

Commit 40473f6

Browse files
committed
added blurb about how only one Future can be returned
1 parent efd3efb commit 40473f6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

documentation/guides/01_async.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ program first_mapping.aleo {
2525
}
2626
```
2727

28-
However, users can only call `transition` functions. In order for the Future generated by an `async function` to be usable, it must be returned by a `transition` function. Any `transition` that calls on an `async function` within its block must be annotated with the `async` keyword and must explicitly return a Future object. Async transitions can return additional data types, including Records, along with a Future object.
28+
However, users can only call `transition` functions. In order for the Future generated by an `async function` to be usable, it must be returned by a `transition` function. Any `transition` that calls on an `async function` within its block must be annotated with the `async` keyword and must explicitly return a Future object. Async transitions can return additional data types in a tuple, including Records, along with a `Future` object. Only one `Future` can be returned. If multiple types are returned, the `Future` must be the last type in the tuple.
2929

3030
```leo
3131
program first_mapping.aleo {

0 commit comments

Comments
 (0)