https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.26.2 2017-10-18T01:46:38+00:00 2017-10-18T01:46:38+00:00 Alex Crichton alex@alexcrichton.com 2017-10-18T01:45:42+00:00 urn:sha1:d9ecdfe3a7a579b9ec89355168f13760c670d4d4 All tests should now have annotation for *why* they're ignored on emscripten. A few tests no longer need such an annotation as well! Closes #41299 2016-09-30T21:02:44+00:00 Ross Schulman ross@rbs.io 2016-09-06T00:00:09+00:00 urn:sha1:b2dfeac6907ab63a3261cfa66c04db239d138433 2015-06-13T11:55:55+00:00 petrochenkov vadim.petrochenkov@gmail.com 2015-06-07T18:00:38+00:00 urn:sha1:bddb685e7322c8ffb9578ae9e5a3a161071b257b 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-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-12-20T02:23:29+00:00 Nick Cameron ncameron@mozilla.com 2014-12-20T02:20:51+00:00 urn:sha1:2e86929a4a5a36f3993e577b4582ba70d84bbb40 This does NOT break any existing programs because the `[_, ..n]` syntax is also supported. 2014-08-21T01:02:23+00:00 Corey Richardson corey@octayn.net 2014-05-27T06:56:52+00:00 urn:sha1:6e8ff999589a7b4c7f62f7128f3e028a7b3ea64f As of RFC 18, struct layout is undefined. Opting into a C-compatible struct layout is now down with #[repr(C)]. For consistency, specifying a packed layout is now also down with #[repr(packed)]. Both can be specified. To fix errors caused by this, just add #[repr(C)] to the structs, and change #[packed] to #[repr(packed)] Closes #14309 [breaking-change] 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-03-01T07:01:54+00:00 Alex Crichton alex@alexcrichton.com 2014-02-28T09:23:06+00:00 urn:sha1:02882fbd7edcb8d0d152afcdc8571216efcbd664 Formatting via reflection has been a little questionable for some time now, and it's a little unfortunate that one of the standard macros will silently use reflection when you weren't expecting it. This adds small bits of code bloat to libraries, as well as not always being necessary. In light of this information, this commit switches assert_eq!() to using {} in the error message instead of {:?}. In updating existing code, there were a few error cases that I encountered: * It's impossible to define Show for [T, ..N]. I think DST will alleviate this because we can define Show for [T]. * A few types here and there just needed a #[deriving(Show)] * Type parameters needed a Show bound, I often moved this to `assert!(a == b)` * `Path` doesn't implement `Show`, so assert_eq!() cannot be used on two paths. I don't think this is much of a regression though because {:?} on paths looks awful (it's a byte array). Concretely speaking, this shaved 10K off a 656K binary. Not a lot, but sometime significant for smaller binaries. 2013-09-25T07:43:37+00:00 Alex Crichton alex@alexcrichton.com 2013-09-25T07:43:37+00:00 urn:sha1:30862a64c29985b044d9bf6f74fcf1394bc145c7 This is required by the check-fast target because each test is slurped up into a submodule.