News for hackers. Stuff that matters.

A comment on A Design Space Exploration of Async/Await. Parent comment

Re:A Design Space Exploration of Async/Await by tcfhgj on Saturday September 12, 2026 @12:58PM (#49674410)
nothing is optimized away, it's just not executed - e.g. the program including semantics of the language is just designed such that it is not executed.

e.g. for Rust/tokio printing B is skipped, because the process exits and cancels the future before the task can print B

[ Parent | on HN ]
Re:A Design Space Exploration of Async/Await by _ink_ on Saturday September 12, 2026 @03:35PM (#49676323)
That's what I thought. But then what is the point when no other async function is executed while the caller sleeps for 1 second (presumably, or is it ms?)?
[ Parent | on HN ]
Re:A Design Space Exploration of Async/Await by tcfhgj on Saturday September 12, 2026 @05:22PM (#49677346)
how would one be executed when the function is explicitly waiting?

also it's an example to demonstrate the differences of async implementations of languages, not a excerpt of a production code base

[ Parent | on HN ]