"how much of stdlib does io things of any kind" A *large* part of stdlib does, as we're noticing while building async-std.
-
-
-
Replying to @ekuber @yoshuawuyts
I would love to see a document where this is collected (minimal info). We already have multiple APIs being hindered from not being able to allocate (IO error? What was the problem? Who knows! We can't afford to allocate a string!) while IO should be similarly avoided in mind.
2 replies 0 retweets 0 likes -
Replying to @ekuber
Practically speaking async-std is pretty much just that — we're not copying over non-io stuff. Which is quite a bit of API already!
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
I think the ideal world we would make the async API be usable from non async scopes without using a reactor (probably with some duplicated APIs for sync and path desugaring tomfoolery) but I don't know if that would be worth the effort.
2 replies 0 retweets 1 like -
Replying to @ekuber @yoshuawuyts
It's only async if it's from the .await region of std, otherwise it's just sync.
2 replies 3 retweets 11 likes
This tweet is perfect.
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.
