which seems like kind of an old version of futures...
# developmenth
hundreds-breakfast-49010
12/03/2019, 10:26 PMwhich seems like kind of an old version of futures to be on, and I wonder if there's any reason we'd want to avoid updating to the latest version - also doesn't using async/await in rust require this?
š 1
e
early-needle-54791
12/03/2019, 10:30 PMIām in favor of updating to new futures / tokio. There are some fs features that would be nice to have.
early-needle-54791
12/03/2019, 10:31 PMbut like you mention not sure how bad it would be to resolve the issues.
h
hundreds-breakfast-49010
12/03/2019, 10:38 PMunfortunately the answer seems to be "a giant pain in the ass", we're using futures 0.1.x all over the place
e
early-needle-54791
12/03/2019, 10:56 PMš
h
hundreds-breakfast-49010
12/03/2019, 11:06 PMit also looks like upgrading
reqwestfuturesw
witty-crayon-22786
12/04/2019, 4:11 AMthis is a split across the entire ecosystem
witty-crayon-22786
12/04/2019, 4:11 AMthe "async/await" on stable milestone a few weeks ago
witty-crayon-22786
12/04/2019, 4:12 AM...was the beginning of a period where everything in the ecosystem will migrate to futures 0.3: ie... "stdlib Future"
witty-crayon-22786
12/04/2019, 4:12 AMtokio was an important milestone... the next thing we'd want to look for will probably be grpc
š 1