News for hackers. Stuff that matters.

A comment on Async-std: an async port of the Rust standard library. Parent comment

Re:Async-std: an async port of the Rust standard library by pohl on Friday August 16, 2019 @04:48PM (#20719553)
The caller of the function knows nothing about what happens within the body of the function. (Is it just doing computation, or is it doing I/O?). The async keyword is how the author of the function makes it explicit that caller should choose when to await the result.

Isn't the alternative WCiYF is proposing to allow the caller to treat any function asynchronously, while having no way to discern whether doing so might be counterproductive?

[ Parent | on HN ]
Re:Async-std: an async port of the Rust standard library by Argorak on Friday August 16, 2019 @05:48PM (#20720033)
Rust async functions are also different here. They don't run the code, they create a Future structure in it's initial state. Contrary to e.g. JavaScript, it doesn't start to run until you end up putting it on an executor. So the actual function call does something very different from what happens in other languages.

It's sometimes called "cold futures".

[ Parent | on HN ]
Re:Async-std: an async port of the Rust standard library by aphexairlines on Friday August 16, 2019 @06:04PM (#20720155)
Sounds similar to what the Scala ecosystem calls Tasks.

https://monix.io/docs/3x/eval/task.html#introduction

https://github.com/traneio/arrows#using-task

[ Parent | on HN ]
Re:Async-std: an async port of the Rust standard library by Argorak on Friday August 16, 2019 @06:21PM (#20720280)
It's similar in some ways, yes. As always, details and labels differ.
[ Parent | on HN ]