https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.22.1 2015-04-09T00:21:34+00:00 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-06-28T18:53:58+00:00 Alex Crichton alex@alexcrichton.com 2014-06-25T19:47:34+00:00 urn:sha1:0dfc90ab15475aa64bea393671463a8e9784ae3f 2014-05-11T08:13:02+00:00 Alex Crichton alex@alexcrichton.com 2014-05-09T17:34:51+00:00 urn:sha1:f94d671bfae5d8e9a4a4add310b1c40af0ab62a6 This commit revisits the `cast` module in libcore and libstd, and scrutinizes all functions inside of it. The result was to remove the `cast` module entirely, folding all functionality into the `mem` module. Specifically, this is the fate of each function in the `cast` module. * transmute - This function was moved to `mem`, but it is now marked as #[unstable]. This is due to planned changes to the `transmute` function and how it can be invoked (see the #[unstable] comment). For more information, see RFC 5 and #12898 * transmute_copy - This function was moved to `mem`, with clarification that is is not an error to invoke it with T/U that are different sizes, but rather that it is strongly discouraged. This function is now #[stable] * forget - This function was moved to `mem` and marked #[stable] * bump_box_refcount - This function was removed due to the deprecation of managed boxes as well as its questionable utility. * transmute_mut - This function was previously deprecated, and removed as part of this commit. * transmute_mut_unsafe - This function doesn't serve much of a purpose when it can be achieved with an `as` in safe code, so it was removed. * transmute_lifetime - This function was removed because it is likely a strong indication that code is incorrect in the first place. * transmute_mut_lifetime - This function was removed for the same reasons as `transmute_lifetime` * copy_lifetime - This function was moved to `mem`, but it is marked `#[unstable]` now due to the likelihood of being removed in the future if it is found to not be very useful. * copy_mut_lifetime - This function was also moved to `mem`, but had the same treatment as `copy_lifetime`. * copy_lifetime_vec - This function was removed because it is not used today, and its existence is not necessary with DST (copy_lifetime will suffice). In summary, the cast module was stripped down to these functions, and then the functions were moved to the `mem` module. transmute - #[unstable] transmute_copy - #[stable] forget - #[stable] copy_lifetime - #[unstable] copy_mut_lifetime - #[unstable] [breaking-change] 2014-02-15T17:11:41+00:00 Corey Richardson corey@octayn.net 2014-02-14T23:42:01+00:00 urn:sha1:49e11630fa84eefc27a34c39ad28a9afb515c5a1 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-18T00:31:35+00:00 Brian Anderson banderson@mozilla.com 2013-10-17T01:34:01+00:00 urn:sha1:34d376f3cf234dc714fcfab7639affd3967dc16d 2013-10-01T06:21:19+00:00 Alex Crichton alex@alexcrichton.com 2013-09-30T02:23:57+00:00 urn:sha1:630082ca8946ff2d0e814a73a2594ba65e1b29be