this post was submitted on 09 Sep 2023
40 points (97.6% liked)

Rust Programming

8176 readers
15 users here now

founded 5 years ago
MODERATORS
nutomic@lemmy.ml
Joe@lemmy.ml
AgreeableLandscape@lemmy.ml
40
Why you might actually want async in your project (notgull.net)
submitted 1 year ago by Sibbo@sopuli.xyz to c/rust@lemmy.ml
8 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] modulus@lemmy.ml 10 points 1 year ago (1 children)

I've had just this case. Wanted to use a particular crate that uses async and it's forcing me to do lots of async things I'm unfamiliar with. I resent it a little, especially for a program that I'm fairly sure will not require concurrency of this sort.

At the same time, maybe I'll get used to async rust if I use it enough. But so far I'm not having a lot of fun with it.

[โ€“] words_number@programming.dev 2 points 1 year ago

It's actually not that hard to use async libraries in sync context. I rarely need that but if I do, I just pull in an executor and write a little extension trait for futures that lets me call .block() instead of .await.