Me: *makes a compiler error* rustc: If I may have your attention for a moment, the paradigm through which you were operating must have been flawed because a lapse of judgement occurred on your part which you can see explained in this book. Me: *runtime panic* libstd: fuck you
-
-
We've started adding this to async-std for our types, with the reasoning that since many errors are relatively uncommon, adding context in specific cases would likely not cause performance slowdown.
@killercup has been taking point on this. Related issue:https://github.com/async-rs/async-std/issues/569 … -
When I saw the original tweet I thought of the same thing but now I'm wondering if we could add feature flags in the std... That way we could have allocating version of IO errors in an opt-in basis...

- 2 more replies
New conversation -
-
-
Yea people don’t want to pay the cost for tracking this info at runtime without opting into it. But I can imagine approaches where you do opt into it somehow
-
I’m thinking a method on io::Error that converts to the io Error with extra info state
End of conversation
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.
