| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2014-11-11 | test: Rename files, fail -> panic. | Michael Sproul | -19/+0 | |
| 2014-10-30 | rollup merge of #18398 : aturon/lint-conventions-2 | Alex Crichton | -2/+2 | |
| Conflicts: src/libcollections/slice.rs src/libcore/failure.rs src/libsyntax/parse/token.rs src/test/debuginfo/basic-types-mut-globals.rs src/test/debuginfo/simple-struct.rs src/test/debuginfo/trait-pointers.rs | ||||
| 2014-10-29 | Rename fail! to panic! | Steve Klabnik | -1/+1 | |
| https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . | xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change] | ||||
| 2014-10-28 | Update code with new lint names | Aaron Turon | -2/+2 | |
| 2014-06-29 | librustc: Remove the fallback to `int` for integers and `f64` for | Patrick Walton | -2/+2 | |
| 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-28 | std: Remove format_strbuf!() | Alex Crichton | -1/+1 | |
| This was only ever a transitionary macro. | ||||
| 2014-05-22 | libstd: Remove `~str` from all `libstd` modules except `fmt` and `str`. | Patrick Walton | -1/+1 | |
| 2014-04-18 | Replace all ~"" with "".to_owned() | Richo Healey | -1/+1 | |
| 2014-04-14 | Use new attribute syntax in python files in src/etc too (#13478) | Manish Goregaokar | -2/+2 | |
| 2013-10-22 | Drop the '2' suffix from logging macros | Alex Crichton | -1/+1 | |
| Who doesn't like a massive renaming? | ||||
| 2013-09-30 | rfail: Remove usage of fmt! | Alex Crichton | -1/+1 | |
| 2013-08-17 | Fix warnings it tests | Erick Tryzelaar | -1/+6 | |
| 2013-05-14 | Use static string with fail!() and remove fail!(fmt!()) | Björn Steinbrink | -1/+1 | |
| fail!() used to require owned strings but can handle static strings now. Also, it can pass its arguments to fmt!() on its own, no need for the caller to call fmt!() itself. | ||||
| 2013-02-13 | Remove die!, raplace invocations with fail! Issue #4524 pt 3 | Nick Desaulniers | -1/+1 | |
| 2013-01-31 | Replace most invocations of fail keyword with die! macro | Nick Desaulniers | -1/+1 | |
| 2012-12-10 | Reliciense makefiles and testsuite. Yup. | Graydon Hoare | -0/+10 | |
| 2012-07-14 | Move the world over to using the new style string literals and types. Closes ↵ | Michael Sullivan | -1/+1 | |
| #2907. | ||||
| 2012-03-22 | make --enforce-mut-vars always on, add mut annotations to remaining files | Niko Matsakis | -1/+3 | |
| 2011-09-11 | Begin valgrinding some run-fail tests that unwind correctly | Brian Anderson | -1/+0 | |
| Issue #236 | ||||
| 2011-09-02 | Reformat. Issue #855 | Brian Anderson | -1/+1 | |
| 2011-08-30 | Support istrs as fail argument. Issue #855 | Brian Anderson | -1/+1 | |
| 2011-08-20 | Reformat | Brian Anderson | -1/+1 | |
| This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[] | ||||
| 2011-08-10 | Begin valgrinding run-fail tests | Brian Anderson | -2/+1 | |
| Introduce a temporary no-valgrind directive for the few that aren't clean | ||||
| 2011-07-27 | Reformat for new syntax | Marijn Haverbeke | -7/+1 | |
| 2011-07-02 | Allow any string expression to be used with fail. | Josh Matthews | -3/+8 | |
| 2011-06-15 | Reformat source tree (minus a couple tests that are still grumpy). | Graydon Hoare | -4/+4 | |
| 2011-06-08 | Add optional message to fail. | Josh Matthews | -0/+5 | |
