https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=master 2018-09-06T11:00:26+00:00 2018-09-06T11:00:26+00:00 Felix S. Klock II pnkfelix@pnkfx.org 2018-08-30T11:16:59+00:00 urn:sha1:7834c2284801766f9925576e8f4d05d7cb7b23dd 2015-04-09T00:21:34+00:00 Alex Crichton alex@alexcrichton.com 2015-04-08T23:27:10+00:00 urn:sha1:ec7c800d2fc0dc5918d325ae68d88c9708d20259 This commit removes pretty-expanded from all tests that wind up calling panic! one way or another now that its internals are unstable. 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-03-23T21:40:26+00:00 Brian Anderson banderson@mozilla.com 2015-03-22T20:13:15+00:00 urn:sha1:8c93a79e387f5197e8b8fe73b3d87d2b101b7c4a Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 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-04-14T15:30:31+00:00 Manish Goregaokar manishsmail@gmail.com 2014-04-14T15:30:31+00:00 urn:sha1:713e87526eac42aa9879e7cfb556ea64d63e7a91 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:19+00:00 Alex Crichton alex@alexcrichton.com 2013-09-30T02:23:57+00:00 urn:sha1:630082ca8946ff2d0e814a73a2594ba65e1b29be 2013-08-17T15:42:35+00:00 Erick Tryzelaar erick.tryzelaar@gmail.com 2013-08-17T15:37:42+00:00 urn:sha1:ad5c67685332dc0e45d459b45749e76c93270988