←back to thread

Flattening Rust’s learning curve

(corrode.dev)
451 points birdculture | 3 comments | 13 May 25 22:25 UTC | HN request time: 0.432s | source
Show context
Havoc ◴[13 May 25 23:42 UTC] No.43979116[source]▶
I thought it was quite manageable at beginner level…though I haven’t dived into async which I gather is a whole different level of pain
replies(1): >>43979133 #
echelon ◴[13 May 25 23:45 UTC] No.43979133[source]▶
Async and the "function color" "problem" fall away if your entire app is in an async runtime.

Almost 90% of the Rust I write these days is async. I avoid non-async / blocking libraries where possible.

I think this whole issue is overblown.

replies(6): >>43979257 #>>43979273 #>>43979433 #>>43979524 #>>43981881 #>>43986031 #
1. spion ◴[14 May 25 00:01 UTC] No.43979257[source]▶
How are async closures / closure types, especially WRT future pinning?
replies(2): >>43979308 #>>43979705 #
2. echelon ◴[14 May 25 00:09 UTC] No.43979308[source]▶
While I'd like to have it, it doesn't stop me from writing a great deal of production code without those niceties.

When it came time for me to undo all the async-trait library hack stuff I wrote after the feature landed in stable, I realized I wasn't really held back by not having it.

3. mplanchard ◴[14 May 25 01:17 UTC] No.43979705[source]▶
Async closures landed in stable recently and have been a nice QoL improvement, although I had gotten used to working around their absence well enough previously that they haven’t been revolutionary yet from the like “enabling new architectural patterns” perspective or anything like that.

I very rarely have to care about future pinning, mostly just to call the pin macro when working with streams sometimes.