about summary refs log tree commit diff
path: root/src/test/compile-fail/issue-897-2.rs
AgeCommit message (Collapse)AuthorLines
2016-08-13Remove invalid compile-fail tests related to `!`Andrew Cann-23/+0
These tests check for the old error messages "`return` in a function declared as diverging" and "computation may converge in a function declared as diverging". The first of these is now invalid as `return` is permitted in functions that return `!`. The second of these is subsumed by the "mismatched types" error.
2014-10-29Rename 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-28Update tests with the new error messagesJakub Bukaj-2/+6
2014-03-28Convert most code to new inner attribute syntax.Brian Anderson-1/+1
Closes #2569
2014-02-12Reenable some ignored test casesFlorian Hahn-16/+3
* src/test/run-pass/issue-3559.rs was fixed in #4726 * src/test/compile-fail/borrowck-call-sendfn.rs was fixed in #2978 * update src/test/compile-fail/issue-5500-1.rs to work with current Rust * removed src/test/compile-fail/issue-5500.rs because it is tested in src/test/run-fail/issue-5500.rs * src/test/compile-fail/view-items-at-top.rs fixed * #897 fixed * compile-fail/issue-6762.rs issue was closed as dup of #6801 * deleted compile-fail/issue-2074.rs because it became irelevant and is irrelevant #2074, a test covering this was added in 4f92f452bd701fb39156d66d4756cc48cc396a8a
2014-02-11Change `xfail` directives in compiletests to `ignore`, closes #11363Florian Hahn-2/+2
2014-02-07Added tests to make tidyDerek Guenther-0/+10
2013-09-23librustc: Change fold to use traits instead of `@fn`.Patrick Walton-0/+4
2013-05-30Promote unreachable code to being a lint attributeAlex Crichton-2/+4
2013-02-13Remove die!, raplace invocations with fail! Issue #4524 pt 3Nick Desaulniers-1/+1
2013-01-31Replace most invocations of fail keyword with die! macroNick Desaulniers-1/+1
2013-01-08Remove ret_style and instead check whether fn return type is botNiko Matsakis-1/+1
cc #3681
2012-12-10Reliciense makefiles and testsuite. Yup.Graydon Hoare-0/+10
2012-08-01Convert ret to returnBrian Anderson-1/+1
2012-06-30change the test suite `//! kind` syntax to `//~ kind` in order to avoid aGareth Daniel Smith-2/+2
conflict with the new single-line-sugared-inner-doc-comment (`//! ...`).
2012-06-18Adding `i` suffixes so cfail tests keep failing after suffix inferenceLindsey Kuper-1/+1
2012-04-06improve error messagesNiko Matsakis-1/+1
2012-03-24correct more broken testsNiko Matsakis-2/+4
2012-03-05rustc: Lower case error messagesBrian Anderson-1/+1
2012-01-20Handle fail after return correctly in typestateTim Chevalier-0/+4
Previously, typestate would conclude that this function was correctly diverging: fn f() -> ! { ret; fail; } even though it always returns to the caller. It wasn't handling the i_diverge and i_return bits correctly in the fail case. Fixed it. Closes #897