This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
at:tutorial:actors [2020/02/05 21:23] elisag |
at:tutorial:actors [2020/02/05 21:26] elisag |
||
---|---|---|---|
Line 194: | Line 194: | ||
+ | |||
+ | |||
+ | <note important> | ||
+ | In AmbientTalk, | ||
+ | </ | ||
==== Enabling futures ==== | ==== Enabling futures ==== | ||
Line 204: | Line 209: | ||
The first statement imports the futures module into the current lexical scope. This enables you as a developer to use some additional language constructs exported by the futures module, as will be explained later. The second statement enables the futures behaviour, causing any asynchronous message send to return a future rather than '' | The first statement imports the futures module into the current lexical scope. This enables you as a developer to use some additional language constructs exported by the futures module, as will be explained later. The second statement enables the futures behaviour, causing any asynchronous message send to return a future rather than '' | ||
+ | |||
+ | < | ||
+ | In what follows we provide an overview on how to work with futures. More information pertaining to the API of the futures language module can be found in the [[: | ||
+ | </ | ||
==== Working with Unresolved Futures ==== | ==== Working with Unresolved Futures ==== |