https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.7.0 2015-01-31T16:40:40+00:00 2015-01-31T16:40:40+00:00 Tobias Bucher tobiasbucher5991@gmail.com 2015-01-31T16:23:42+00:00 urn:sha1:b4a43f3864e394959a7d3c3efae6da85bdc59c71 2015-01-06T21:48:33+00:00 Corey Richardson corey@octayn.net 2014-12-06T02:12:25+00:00 urn:sha1:5a4ca319185a3f399986bc5e5a2d0a96fac583ae 2014-08-28T01:46:52+00:00 Niko Matsakis niko@alum.mit.edu 2014-08-28T01:46:52+00:00 urn:sha1:1b487a890695e7d6dfbfe5dcd7d4fa0e8ca8003f 2014-06-29T18:47:58+00:00 Patrick Walton pcwalton@mimiga.net 2014-06-27T19:30:25+00:00 urn:sha1:a5bb0a3a4574af88add700ace7aefc37172fa7a5 floating point numbers for real. This will break code that looks like: let mut x = 0; while ... { x += 1; } println!("{}", x); Change that code to: let mut x = 0i; while ... { x += 1; } println!("{}", x); Closes #15201. [breaking-change] 2014-05-15T20:50:42+00:00 Felix S. Klock II pnkfelix@pnkfx.org 2014-05-05T15:00:14+00:00 urn:sha1:3aad0e249cebaf2123cd875b737c088ae2c48728 Each test works by rendering the flowgraph for the last identified block we see in expanded pretty-printed output, and comparing it (via `diff`) against a checked in "foo.dot-expected.dot" file. Each test post-processes the output to remove NodeIds ` (id=NUM)` so that the expected output is somewhat stable (or at least independent of how we assign NodeIds) and easier for a human to interpret when looking at the expected output file itself. ---- Test writing style notes: I usually tried to write the tests in a way that would avoid duplicate labels in the output rendered flow graph, when possible. The tests that have string literals "unreachable" in the program text are deliberately written that way to remind the reader that the unreachable nodes in the resulting graph are not an error in the control flow computation, but rather a natural consequence of its construction.