| Age | Commit message (Collapse) | Author | Lines |
|---|
|
This "bubble up an error" macro was originally named if_ok! in order to get it
landed, but after the fact it was discovered that this name is not exactly
desirable.
The name `if_ok!` isn't immediately clear that is has much to do with error
handling, and it doesn't look fantastic in all contexts (if if_ok!(...) {}). In
general, the agreed opinion about `if_ok!` is that is came in as subpar.
The name `try!` is more invocative of error handling, it's shorter by 2 letters,
and it looks fitting in almost all circumstances. One concern about the word
`try!` is that it's too invocative of exceptions, but the belief is that this
will be overcome with documentation and examples.
Close #12037
|
|
Most of them are to reduce warnings in testing builds.
|
|
I've forgot why we keep them, so let me know if you know their reason
for existing.
Signed-off-by: OGINO Masanori <masanori.ogino@gmail.com>
|
|
Poly and String have polymorphic `impl`s and so require different method
names.
|
|
|
|
|
|
Done as a part of #8784.
Signed-off-by: OGINO Masanori <masanori.ogino@gmail.com>
|
