sebsch@discuss.tchncs.de to Programming@programming.dev · 11 months agoLet futures be futureswithout.boatsexternal-linkmessage-square6fedilinkarrow-up133arrow-down11cross-posted to: hackernews@lemmy.smeargle.fansrust@programming.dev
arrow-up132arrow-down1external-linkLet futures be futureswithout.boatssebsch@discuss.tchncs.de to Programming@programming.dev · 11 months agomessage-square6fedilinkcross-posted to: hackernews@lemmy.smeargle.fansrust@programming.dev
minus-squarecodemonk@programming.devlinkfedilinkarrow-up11·11 months agoI would not call it a bash. Go’s approach naturally comes up in discussions on async Rust. Thus, it makes sense to at least briefly mentioning the trade-offs that approach has.
I would not call it a bash. Go’s approach naturally comes up in discussions on async Rust. Thus, it makes sense to at least briefly mentioning the trade-offs that approach has.