sebsch@discuss.tchncs.de to Programming@programming.dev · 3 years agoLet futures be futureswithout.boatsexternal-linkmessage-square7linkfedilinkarrow-up128arrow-down11cross-posted to: rust@programming.dev
arrow-up127arrow-down1external-linkLet futures be futureswithout.boatssebsch@discuss.tchncs.de to Programming@programming.dev · 3 years agomessage-square7linkfedilinkcross-posted to: rust@programming.dev
minus-squarecodemonk@programming.devlinkfedilinkarrow-up9·3 years 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.