|
@yoshuawuyts | |||||
|
`.await` syntax landed in nightly, and will likely be included in tomorrow's release. If you want to move your `await!()` code to use `.await`, taiki-e wrote a migration tool to make this easy!
github.com/taiki-e/replac…
cc/ @rustlang @RustNetWG
|
||||||
|
||||||
|
yosh
@yoshuawuyts
|
9. svi |
|
Taiki now has a Twitter account, you can follow them as @_taiki_e!
|
||
|
|
||
|
yosh
@yoshuawuyts
|
8. svi |
|
I don't know Tokio's migration roadmap, but with the Futures compat layer it should be possible to use 0.1 Futures with `.await`.
Alternatively it's possible to use Tokio's networking stack through Runtime, which will be compatible with `.await` once it goes live.
|
||
|
|
||
|
ᴋᴏɴ of 2020
@GolDDranks
|
9. svi |
|
Taiki-e for sure is a power player! Do you happen to know whether they live near Tokyo? (he seems to be Japanese?) We are organising Rust meetups there and it would be nice to meet and maybe hear something about the futures work.
|
||
|
|
||
|
yosh
@yoshuawuyts
|
9. svi |
|
I don't know where they're based, but I've passed along the message (:
|
||
|
|
||
|
Marcel Buesing
@marcelbuesing
|
9. svi |
|
Just used the tool to migrate a project and I feel the new syntax looks quite good in the diff
|
||
|
|
||
|
Douman Ashiya | 道満 蘆屋
@DoumanAsh
|
8. svi |
|
Sad day, guess I'll have to use my own await macro
|
||
|
|
||