Sibbo@sopuli.xyz to Rust Programming@lemmy.ml · 1 year agoWhy you might actually want async in your projectnotgull.netexternal-linkmessage-square8fedilinkarrow-up141cross-posted to: rust@programming.devhackernews@lemmy.smeargle.fanstechnews@radiation.partyhackernews@derp.foo
arrow-up141external-linkWhy you might actually want async in your projectnotgull.netSibbo@sopuli.xyz to Rust Programming@lemmy.ml · 1 year agomessage-square8fedilinkcross-posted to: rust@programming.devhackernews@lemmy.smeargle.fanstechnews@radiation.partyhackernews@derp.foo
minus-squarewords_number@programming.devlinkfedilinkarrow-up2·1 year agoIt’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.
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.