sebsch to Programming@programming.dev · 11 months agoLet futures be futureswithout.boatsexternal-linkmessage-square6fedilinkarrow-up135arrow-down11cross-posted to: hackernews@lemmy.smeargle.fansprogramminglanguages@lemmit.onlinerust@programming.devrust@lemmit.online
arrow-up134arrow-down1external-linkLet futures be futureswithout.boatssebsch to Programming@programming.dev · 11 months agomessage-square6fedilinkcross-posted to: hackernews@lemmy.smeargle.fansprogramminglanguages@lemmit.onlinerust@programming.devrust@lemmit.online
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.