Let futures be futures

Re:Let futures be futures by n1c00o on Saturday February 03, 2024 @06:09PM (#39245709)

Really good critique of the current state of handling, but my opinion is still that the language should not itself makes any design decision on async. I believe everything should just keep being a set of instructions that are executed accordingly to the machine, and that's it. It helps ensuring the language semantics are still relevant on newer execution machines.

Indeed, async v. sync should be a matter of the application and the application only.

[ Parent | on HN ]

Re:Let futures be futures by Rusky on Saturday February 03, 2024 @08:22PM (#39246580)

This is like arguing for goto over structured concurrency. Async/await is a structured control flow primitive that lets you compose functions in more flexible ways. It will stay relevant as long as we still use things like functions, branching, and looping.

[ Parent | on HN ]