- 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 4月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
-
- 27 11月, 2013 1 次提交
-
-
由 Patrick Walton 提交于
-
- 22 10月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
Who doesn't like a massive renaming?
-
- 01 10月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
-
- 24 9月, 2013 1 次提交
-
-
由 Patrick Walton 提交于
-
- 03 9月, 2013 1 次提交
-
-
由 Huon Wilson 提交于
-
- 04 5月, 2013 1 次提交
-
-
由 Daniel Micay 提交于
-
- 03 3月, 2013 1 次提交
-
-
由 Patrick Walton 提交于
-
- 14 2月, 2013 1 次提交
-
-
由 Nick Desaulniers 提交于
-
- 02 2月, 2013 1 次提交
-
-
由 Graydon Hoare 提交于
-
- 01 2月, 2013 1 次提交
-
-
由 Nick Desaulniers 提交于
-
- 11 12月, 2012 1 次提交
-
-
由 Graydon Hoare 提交于
-
- 13 4月, 2012 1 次提交
-
-
由 Tim Chevalier 提交于
Add a run-fail test for result::get, get rid of a FIXME. Also some random other tests, mostly xfailed.
-