7bb498bd7a
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 |
||
---|---|---|
.. | ||
comm | ||
fmt | ||
io | ||
num | ||
path | ||
rand | ||
rt | ||
sync | ||
unstable | ||
any.rs | ||
ascii.rs | ||
bool.rs | ||
c_str.rs | ||
cast.rs | ||
cell.rs | ||
char.rs | ||
cleanup.rs | ||
clone.rs | ||
cmp.rs | ||
container.rs | ||
default.rs | ||
from_str.rs | ||
gc.rs | ||
hash.rs | ||
hashmap.rs | ||
iter.rs | ||
kinds.rs | ||
lib.rs | ||
libc.rs | ||
local_data.rs | ||
logging.rs | ||
macros.rs | ||
managed.rs | ||
mem.rs | ||
ops.rs | ||
option.rs | ||
os.rs | ||
owned.rs | ||
prelude.rs | ||
ptr.rs | ||
rc.rs | ||
reference.rs | ||
reflect.rs | ||
repr.rs | ||
result.rs | ||
rtdeps.rs | ||
run.rs | ||
str.rs | ||
task.rs | ||
to_bytes.rs | ||
to_str.rs | ||
trie.rs | ||
tuple.rs | ||
unicode.rs | ||
unit.rs | ||
vec_ng.rs | ||
vec.rs |