It's interesting to see people complain about potential implicit end of function ergonomics features in @rustlang, ignoring that a lot of the modern language practice is based on similar things, e.g.:
* Deref
* ? with implicit From conversion
* Reborrow
* match ergonomics
I always think of the context method to provide a typed history of sorts for errors you encounter. Helps clarify the origin of the error It's close, but think it's slightly different from what you meant. https://paper.dropbox.com/doc/How-To-Failure-Vb2j93CuQKwLR57xX5dUF … has some more on it.
-
-
(hope my words make sense here, haha)
-
Not sure I really get it but it's my fault, I'm also working on other stuff right now
failure's Fail::context allows you to supply context to your result -- but `.try_into()?` can already give you a pretty specific error. Can you give an example where you'd need more context? - 2 more replies
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.