rust/src/test/run-pass/tuple-struct-constructor-pointer.rs, branch 1.25.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.25.02015-03-26T19:10:22+00:00Mass rename uint/int to usize/isize2015-03-26T19:10:22+00:00Alex Crichtonalex@alexcrichton.com2015-03-26T00:06:52+00:00urn:sha1:43bfaa4a336095eb5697fb2df50909fd3c72ed14
Now that support has been removed, all lingering use cases are renamed.
s/Show/Debug/g2015-01-29T12:49:02+00:00Jorge Apariciojaparicious@gmail.com2015-01-28T13:34:18+00:00urn:sha1:788181d4055747b5307f186a873ab5d2acd29994Use `derive` rather than `deriving` in tests2015-01-02T10:05:22+00:00Nick Cameronncameron@mozilla.com2014-12-31T04:32:49+00:00urn:sha1:30e149231c627e61524d1b5bd6357886befae9e6std: Rename {Eq,Ord} to Partial{Eq,Ord}2014-05-30T22:52:24+00:00Alex Crichtonalex@alexcrichton.com2014-05-30T00:45:07+00:00urn:sha1:748bc3ca49de8ab0b890726120c40567094e43fc
This is part of the ongoing renaming of the equality traits. See #12517 for more
details. All code using Eq/Ord will temporarily need to move to Partial{Eq,Ord}
or the Total{Eq,Ord} traits. The Total traits will soon be renamed to {Eq,Ord}.
cc #12517
[breaking-change]
std: Change assert_eq!() to use {} instead of {:?}2014-03-01T07:01:54+00:00Alex Crichtonalex@alexcrichton.com2014-02-28T09:23:06+00:00urn: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.
All uses of `extern fn` should mean `extern "C" fn`. Closes #9309.2014-02-24T00:24:57+00:00Nick Cameronncameron@mozilla.com2014-02-14T04:23:01+00:00urn:sha1:317a253b22a512fad46c3749ea86d9674ff18453Fix run-pass tests to have 'pub fn main'2013-09-25T07:43:37+00:00Alex Crichtonalex@alexcrichton.com2013-09-25T07:43:37+00:00urn:sha1:30862a64c29985b044d9bf6f74fcf1394bc145c7
This is required by the check-fast target because each test is slurped up into a
submodule.
Add assertions to test2013-08-18T19:37:40+00:00Andreas Martensandreasm@fastmail.fm2013-08-18T19:37:40+00:00urn:sha1:29ab2daa5efebb59b5ad4a2710d570e89696e583Fix segfault when calling tuple struct constructor as extern fn2013-08-17T20:42:31+00:00Andreas Martensandreasm@fastmail.fm2013-08-17T20:42:31+00:00urn:sha1:c4b4cb36c83f1fe581dc9d20c25baa2d2ed23e42
Fixes #5315