"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 @yoshuawuyts
If we did that, them we could have 4 levels of std libs: - no_std/core - no IO - no alloc - nice high level API for app devs
1 reply 0 retweets 2 likes -
Replying to @ekuber @yoshuawuyts
This would make it hard for some because many libs would cater the latter and forego all others (we already see this is with no_std)
1 reply 0 retweets 1 like -
Replying to @ekuber @yoshuawuyts
But if we managed to make it easier to control, (probably by making it explicit in cargo.toml) we could suddenly remove a whole layer of ergonomics problems in std
1 reply 0 retweets 1 like -
Replying to @ekuber @yoshuawuyts
And we could make the APIs the a strict superset of the prior layer, so that turning an "all bells and whistles" crate into a non-alloc/non-io crate is as easy as possible we could have our cake and eat it too.
1 reply 0 retweets 1 like
This would be really interesting to explore further!!
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.
