Lmao, so there's no need to define an `async_std` version of `write!` because the std macro is already compatible with async functions. Only difference is that if you call it on any of async_std's types you need to suffix it with `.await`.
-
-
The documentation seems to be a bit misleading though. I guess "this method will not return until" is supposed to say "the returned future will not resolve until"?
-
Fair enough; updated the description
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.