| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2014-02-23 | auto merge of #12328 : nick29581/rust/abi, r=alexcrichton | bors | -2/+2 | |
| 2014-02-24 | All uses of `extern fn` should mean `extern "C" fn`. Closes #9309. | Nick Cameron | -2/+2 | |
| 2014-02-23 | Merge remote-tracking branch 'brson/ratcher' | Brian Anderson | -1/+1 | |
| 2014-02-22 | Warn about unnecessary parentheses upon assignment | Eduard Bopp | -1/+1 | |
| Closes #12366. Parentheses around assignment statements such as let mut a = (0); a = (1); a += (2); are not necessary and therefore an unnecessary_parens warning is raised when statements like this occur. The warning mechanism was refactored along the way to allow for code reuse between the routines for checking expressions and statements. Code had to be adopted throughout the compiler and standard libraries to comply with this modification of the lint. | ||||
| 2014-02-21 | test: 'ratcher' is not a word | Brian Anderson | -1/+1 | |
| 2014-02-21 | Move time out of extra (cc #8784) | Arcterus | -1/+2 | |
| 2014-02-20 | Mass rename if_ok! to try! | Alex Crichton | -46/+46 | |
| This "bubble up an error" macro was originally named if_ok! in order to get it landed, but after the fact it was discovered that this name is not exactly desirable. The name `if_ok!` isn't immediately clear that is has much to do with error handling, and it doesn't look fantastic in all contexts (if if_ok!(...) {}). In general, the agreed opinion about `if_ok!` is that is came in as subpar. The name `try!` is more invocative of error handling, it's shorter by 2 letters, and it looks fitting in almost all circumstances. One concern about the word `try!` is that it's too invocative of exceptions, but the belief is that this will be overcome with documentation and examples. Close #12037 | ||||
| 2014-02-20 | move extra::test to libtest | Liigo Zhuang | -0/+1577 | |
