- 04 3月, 2017 1 次提交
-
-
由 Taylor Cramer 提交于
-
- 27 3月, 2015 1 次提交
-
-
由 Alex Crichton 提交于
Now that support has been removed, all lingering use cases are renamed.
-
- 18 2月, 2015 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 29 10月, 2014 1 次提交
-
-
由 Steve Klabnik 提交于
https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . | xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change]
-
- 08 2月, 2014 1 次提交
-
-
由 Derek Guenther 提交于
-
- 22 10月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
Who doesn't like a massive renaming?
-
- 01 10月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
-
- 17 8月, 2013 1 次提交
-
-
由 Erick Tryzelaar 提交于
-
- 14 5月, 2013 1 次提交
-
-
由 Björn Steinbrink 提交于
fail!() used to require owned strings but can handle static strings now. Also, it can pass its arguments to fmt!() on its own, no need for the caller to call fmt!() itself.
-
- 15 2月, 2013 2 次提交
-
-
由 Patrick Walton 提交于
-
由 Patrick Walton 提交于
-
- 14 2月, 2013 1 次提交
-
-
由 Nick Desaulniers 提交于
-
- 11 12月, 2012 1 次提交
-
-
由 Brian Anderson 提交于
-