https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=release-0.2 2011-08-20T18:04:00+00:00 2011-08-20T18:04:00+00:00 Brian Anderson banderson@mozilla.com 2011-08-19T22:16:48+00:00 urn:sha1:518dc52f85c2efb67aaa1208c02e9a7e0bdaca49 This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[] 2011-08-03T17:55:59+00:00 Brian Anderson banderson@mozilla.com 2011-08-03T06:46:52+00:00 urn:sha1:c53402846ea7fabe8595c3f50cbc786db16d087a While it is still technically possible to test stage 0, it is not part of any of the main testing rules and maintaining xfail-stage0 is a chore. Nobody should worry about how tests fare in stage0. 2011-07-27T13:54:33+00:00 Marijn Haverbeke marijnh@gmail.com 2011-07-27T12:19:39+00:00 urn:sha1:df7f21db093b0f206048b18e977161f91b7c28f1 2011-07-03T18:51:47+00:00 Tim Chevalier chevalier@alum.wellesley.edu 2011-07-03T17:39:07+00:00 urn:sha1:046c25dbc0c11dcc467c4ff22b8bfbd853976b5b An expression like: foo(1, fail, 2) was failing to parse, because the parser was interpreting the comma as the start of an expression that was an argument to fail, rather than recognizing that the fail here has no arguments Fixed this by using can_begin_expr to determine whether the next token after a fail token suggests that this is a nullary fail or a unary fail. In addition, when translating calls, check before translating each argument that the block still isn't terminated. This has the effect that if an argument list includes fail, the back-end won't keep trying to generate code for successive arguments and trip the !*terminated assertion.