sebsch@discuss.tchncs.de to Programming@programming.dev · 1 year agoLet futures be futureswithout.boatsexternal-linkmessage-square6fedilinkarrow-up135arrow-down11cross-posted to: rust@programming.dev
arrow-up134arrow-down1external-linkLet futures be futureswithout.boatssebsch@discuss.tchncs.de to Programming@programming.dev · 1 year agomessage-square6fedilinkcross-posted to: rust@programming.dev
minus-squarecodemonk@programming.devlinkfedilinkarrow-up11·1 year 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.