A Design Space Exploration of Async/Await

Re:A Design Space Exploration of Async/Await by mitxela on Saturday September 12, 2026 @12:15PM (#49673918)

I felt like they were reaching deep to find dimensions. Whether a task runs autonomously or needs its parent to poll it (Rust) is a dimension but whether an autonomous running task can continue after being cancelled shouldn't be - if you go into that much detail you could probably find thousands of dimensions. If it's autonomous it can do whatever it wants to.

[ Parent | on HN ]

Re:A Design Space Exploration of Async/Await by msteffen on Saturday September 12, 2026 @08:01PM (#49678523)

> whether an autonomous running task can continue after being cancelled shouldn't be

Idk, I think this might be quite important in servers, or any application where the running task might spawn subprocesses (can those continue autonomously?) or block on/use os resources

[ Parent | on HN ]

Re:A Design Space Exploration of Async/Await by antonvs on Saturday September 12, 2026 @08:18PM (#49678609)

Full lifecycle management of async tasks is a pretty important aspect - one might even say dimension - of the problem.

[ Parent | on HN ]

Re:A Design Space Exploration of Async/Await by mitxela on Sunday September 13, 2026 @04:18AM (#49681369)

And either the runtime enforces it or it doesn't and just notifies you, but I think whether it notifies you once or continually is not a relevant dimension.

[ Parent | on HN ]