Tracking issue for rust-lang/rfcs#243 and rust-lang/rfcs#1859.
Implementation concerns:
?
operator that is roughly equivalent to try!
- implement the ?
operator #31954try { ... }
expression - implement catch
expressions #39849
do catch { ... }
syntax question
catch
blocks are not Ok
-wrapping their value #41414, now being settled anew in Resolving Ok
-wrapping for try
blocks #70941)ExprWithBlock
, so works in a match arm without a commatry { expr? }?
currently requires an explicit type annotation somewhere).Try
trait ( extend ?
to operate over other types rfcs#1859)
Try
trait (in place of Carrier
) and convert ?
to use it ( Lower ?
to Try
instead of Carrier
#42275)Option
and so forth, and a suitable family of tests ( Impl Try for Option #42526)?
error messages per RFC 1859 #35946)try
in new editiontry{}catch
(or other following idents) to leave design space open for the future, and point people to how to do what they want with match
insteadchpio, Darkeye9, updogliu, Object905, Radviger and 392 moredsgallups, davidsenk and Mirsariochriskrycho, EdorianDark, yberreby, lambda-fairy, tanakh and 92 morepaomian, sunjay, mfarrugi, Dushistov, MOZGIII and 16 morecolin-kiegel, repax, alexander-irbis, NotIntMan, JesseWright and 81 morebakcxoj, JustAPerson, nazar-pc, museun, JarvisCraft and 47 moreKrantz-XRF, ishantheperson, Virgiel, lukechu10, WilliamVenner and 30 more
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4