rust/src/libcoretest/fmt/mod.rs, branch 1.2.0 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.2.0 2015-07-08T21:39:02+00:00 std: Fix formatting flags for chars 2015-07-08T21:39:02+00:00 Alex Crichton alex@alexcrichton.com 2015-07-01T02:26:03+00:00 urn:sha1:8dff253d243615ac4c35f59598d0d36034f91ecd This recently regressed in #24689, and this updates the `Display` implementation to take formatting flags into account. Closes #26625 Implement RFC 640 2015-03-10T06:24:34+00:00 Steven Fackler sfackler@gmail.com 2015-03-07T05:16:44+00:00 urn:sha1:e3656bd81baa3c2cb5065da04f9debf378f99772 Clean up `isize`, `usize`. Don't bench allocation but formatting. 2015-01-23T11:35:52+00:00 Tobias Bucher tobiasbucher5991@gmail.com 2015-01-23T01:08:21+00:00 urn:sha1:d909dad0667db82576e2d1bc2df1f0f30023d0e8 coretest: Ensure that pointer formatting flags are cleaned up 2014-09-09T19:34:41+00:00 Piotr Czarnecki pioczarn@gmail.com 2014-08-25T13:31:42+00:00 urn:sha1:fcf88b8f87597f97112f048eaa296b3127e51d0b Extract tests from libcore to a separate crate 2014-06-29T22:57:21+00:00 Steven Fackler sfackler@gmail.com 2014-06-28T20:57:36+00:00 urn:sha1:1ed646eaf7d09455a086afa11bcd83a7d2a6b0f4 Libcore's test infrastructure is complicated by the fact that many lang items are defined in the crate. The current approach (realcore/realstd imports) is hacky and hard to work with (tests inside of core::cmp haven't been run for months!). Moving tests to a separate crate does mean that they can only test the public API of libcore, but I don't feel that that is too much of an issue. The only tests that I had to get rid of were some checking the various numeric formatters, but those are also exercised through normal format! calls in other tests.