News for hackers. Stuff that matters.
Re:The Rust I wanted had no future by lmm on Monday June 05, 2023 @07:46PM (#36206014)
Does blocking I/O or not is very much a property of the function itself, as is "may finish up running on a different thread from the one it started on" (or, if you prefer, "needs to be run under a runtime that provides that capability").

Sending a letter and getting a reply is an inherently async action; you can stare at the mailbox all day but you probably don't want to. Waiting in line at the bank is inherently sync; if you try to do something else and then come back they'll make you start over again.

Re:The Rust I wanted had no future by divan on Tuesday June 06, 2023 @09:20AM (#36212256)
> you can stare at the mailbox all day but you probably don't want to

Yet, it's up to me to decide, not to the mailbox.

Re:The Rust I wanted had no future by lmm on Tuesday June 06, 2023 @05:52PM (#36219554)
You can always call blocking await on an async function. It's just usually a bad idea.