Note that while currently the only items `IntoStream` is implemented for is `Vec`, we plan to add it to more types. Which means it'll soon be possible to e.g. have two streams, call `zip` on them to convert them to a single stream of tuples, and `collect` that into a hashmap.
-
-
Show this thread
-
Anyway, this is core building block #2 on the list. On to building 3 and 4 now.https://twitter.com/yoshuawuyts/status/1173502686257434625 …
Show this thread
End of conversation
New conversation -
-
-
I knew the 2018 edition integrated macros into the module system but that's the first time I've seen a macro invoked by path. Neat.
-
Heh yeah, so the only way I could get this to work was by re-exporting them from a different crate
(in our case we have async-macros for this) - 2 more replies
New conversation -
-
-
Question from a causal observer's perspective. Is async-std a complement or alternative to the futures crates and how do the two relate going forward? Planning out some future this and forecasting my dependencies.
-
It compliments `futures-core`, but is an alternative to `futures`. We provide full interoperability with the core traits, but for the purpose of stdlib parity we had to define the rest of the types ourselves. My hope is to see the futures-core traits become part of nightly.
- 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.