|
04:27
swaggboi left
04:30
swaggboi joined
07:37
dakkar joined
12:05
dakkar left,
dakkar joined
14:37
Guest55 joined,
Guest55 left
14:38
Guest51 joined
|
|||
| Guest51 | docs only mention await working with Channels and Promises, but something like await $existing-supply.first; seems to work even though Supply.first returns another Supply. Will using await that way come back to haunt me? | 14:46 | |
|
15:28
human-blip left
15:31
human-blip joined
15:43
human-blip left
15:45
human-blip joined
|
|||
| lizmat | you can check if something does the Awaitable role (which I just realize is not documented) | 16:08 | |
|
16:18
dakkar left
|
|||
| Guest51 | okay, thank you. Is the intended behavior to return the Supply's final value when done? | 16:52 | |
| lizmat | I think so...what does the doc say ? | 17:01 | |
|
17:05
Guest51 left
17:08
Guest99 joined
|
|||
| Guest99 | back from being disconnected. Awaitable isn't documented, nor is the behavior for using await on Supply. The source for Supply-coercers has SupplyAwaitableHandle.subscribe-awaiter but I wasn't sure I followed everything correctly. | 17:15 | |
| lizmat | a doc issue has been made: github.com/Raku/doc/issues/2874 | 17:18 | |
| actually, a long time ago already I now see :-( | 17:19 | ||
| anyways, you can call $foo.await when $foo ~~ Awaitable is true | |||
| Guest99 | okay, thanks again. | 17:20 | |
|
17:23
Guest99 left
17:44
sjn left,
sjn joined
22:55
human-blip left
22:57
human-blip joined
|
|||