> 1. Avoid Turning Functions into async Whenever Possible
> Consider the following example:
Has the author benchmarked this? They are essentially replicating what the compiler does already: the compiler doesn't put each statement/expression into its own state, states occur on the boundaries of awaits.
I wouldn't even feel confident in assuming that the compiler wouldn't inline the function they've defined, a one-liner that's only called from a single location. It wouldn't surprise me at all if the compiler produced exactly the same code for the two examples.
I think he's trying to suggest not making a few function without any await statements async. He doesn't suggest implementing your own futures manually.
I have never seen a site stretching words like this. Increasing the spacing between words is already going away (thankfully), but increasing the spacing between characters... why?
zamalek|8 months ago
> Consider the following example:
Has the author benchmarked this? They are essentially replicating what the compiler does already: the compiler doesn't put each statement/expression into its own state, states occur on the boundaries of awaits.
saghm|8 months ago
surajrmal|8 months ago
dkersten|8 months ago
C and C++ will outlast us all and there are many other languages vying to be the successor, not just Rust.
remram|8 months ago
https://imgur.com/a/smQo87s