Alex Crichton 7bb498bd7a Mass rename if_ok! to try!
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
2014-02-20 09:16:52 -08:00
..
2014-02-20 09:16:52 -08:00
2014-02-20 09:16:52 -08:00
2014-02-20 16:03:58 +08:00
2014-02-20 16:03:58 +08:00
2014-02-20 16:03:58 +08:00
2014-02-20 16:03:58 +08:00
2014-02-18 08:05:35 +11:00
2014-02-20 16:03:58 +08:00
2014-02-13 12:54:17 -08:00
2014-02-13 20:12:59 -05:00
2014-02-20 09:16:52 -08:00
2014-02-18 08:05:35 +11:00
2014-02-14 23:49:22 -08:00
2014-02-19 01:10:31 -08:00
2014-02-14 23:49:22 -08:00
2014-02-20 09:16:52 -08:00
2014-02-15 12:11:41 -05:00
2014-02-20 16:03:58 +08:00
2014-02-20 16:03:58 +08:00
2014-02-15 12:11:41 -05:00
2014-02-15 12:11:41 -05:00
2014-02-13 12:54:17 -08:00
2014-02-20 09:16:52 -08:00
2014-02-14 08:07:46 -08:00
2014-02-20 16:03:58 +08:00
2014-02-20 16:03:58 +08:00
2014-02-20 09:16:52 -08:00
2014-02-15 12:11:41 -05:00
2014-02-20 09:16:52 -08:00