https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.1.0 2015-03-26T19:10:22+00:00 2015-03-26T19:10:22+00:00 Alex Crichton alex@alexcrichton.com 2015-03-26T00:06:52+00:00 urn:sha1:43bfaa4a336095eb5697fb2df50909fd3c72ed14 Now that support has been removed, all lingering use cases are renamed. 2015-02-18T14:10:10+00:00 Niko Matsakis niko@alum.mit.edu 2015-02-18T10:42:01+00:00 urn:sha1:72eb214ee473e7fbb8fb27ba10d6e43d02bb633b 2014-10-29T15:43:07+00:00 Steve Klabnik steve@steveklabnik.com 2014-10-09T19:17:22+00:00 urn:sha1:7828c3dd2858d8f3a0448484d8093e22719dbda0 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] 2014-02-07T18:49:24+00:00 Derek Guenther dguenther9@gmail.com 2014-02-05T22:33:10+00:00 urn:sha1:730bdb6403dd47b98c1be6c4b3423edb28ca9477 2013-10-22T15:09:56+00:00 Alex Crichton alex@alexcrichton.com 2013-10-21T20:08:31+00:00 urn:sha1:daf5f5a4d10513ff42e79fa7ef8819b170f3a13d Who doesn't like a massive renaming? 2013-10-01T06:21:20+00:00 Alex Crichton alex@alexcrichton.com 2013-09-30T04:08:46+00:00 urn:sha1:02054ac8a1490211a5a6873fdefe186bd0758b7b 2013-08-17T15:42:35+00:00 Erick Tryzelaar erick.tryzelaar@gmail.com 2013-08-17T15:37:42+00:00 urn:sha1:ad5c67685332dc0e45d459b45749e76c93270988 2013-05-14T14:36:23+00:00 Björn Steinbrink bsteinbr@gmail.com 2013-05-05T22:18:51+00:00 urn:sha1:bdc182cc41c2741edc6fdc4ec09b8522479aab40 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. 2013-02-14T22:44:12+00:00 Patrick Walton pcwalton@mimiga.net 2013-02-14T19:47:00+00:00 urn:sha1:9143688197ee1ba14e224badbe1402b36111e592 2013-02-14T01:01:32+00:00 Nick Desaulniers ndesaulniers@mozilla.com 2013-02-12T03:26:38+00:00 urn:sha1:4445b38df27777b043cad9ecc2452daad3469949