Rust twitter people :)
Good reputable replacement for io::Read/Write for no_std / alloc only?
There's `rust-core_io` but it's nightly only.
@rustlang
-
-
I've really wished these traits were in `core` or `alloc`
2 replies 1 retweet 6 likes -
I disagree. `io::Error`s and everything in the io module has an extremely bad API and is justified only because of compatibility with the bad APIs of operating systems. Putting them in core is just the lazy option. We can do better.
2 replies 0 retweets 3 likes -
My take: it was the best we could do at the time. Maybe it could be better today. It certainly has weak spots.
2 replies 0 retweets 4 likes -
Replying to @steveklabnik @tomaka17 and
Is there a pre-RFC trying to put some ideas about a new design for them?
1 reply 0 retweets 0 likes -
Replying to @Gr4y_J4ck @tomaka17 and
I don’t think so; I’m not sure that the churn would be worth it. The APIs aren’t horrible!
2 replies 0 retweets 4 likes -
Replying to @steveklabnik @Gr4y_J4ck and
I am so used to I/O APIs being the most horrible thing ever std::io really isn't that bad, IMNSHO. The real problems are all of the sharp corners of blocking I/O no one ever acknowledges, and async/await is already the "redesign"
1 reply 0 retweets 3 likes
Rust’s I/O is just fine. “Extremely bad API” is a silly take IMO.
-
-
Replying to @pcwalton @steveklabnik and
old_io was a bit bonkers. What shipped as std::io in Rust 1.0 is significantly better than "BSD sockets wrappers" et all in most languages I've ever used
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.