rust/src/test/ui/binding/expr-match-unique.rs

// run-pass
#![feature(box_syntax)]

// Tests for match as expressions resulting in boxed types
fn test_box() {
    let res: Box<_> = match true { true => { box 100 }, _ => panic!() };
    assert_eq!(*res, 100);
}

pub fn main() { test_box(); }
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 14:18:55 +02:00			`// run-pass`
fallout: run-pass tests that use box. (many could be ported to `Box::new` instead in the future.) 2015-01-08 02:25:56 +01:00			`#![feature(box_syntax)]`
Create a bunch of test cases for unique boxes by copying box tests XFAIL the ones that don't work Issue #409 2011-09-23 14:58:06 -07:00
Convert alt to match. Stop parsing alt 2012-08-06 12:34:08 -07:00			`// Tests for match as expressions resulting in boxed types`
Rewrite exhaustiveness checker Issue #352 Closes #1720 The old checker would happily accept things like 'alt x { @some(a) { a } }'. It now properly descends into patterns, checks exhaustiveness of booleans, and complains when number/string patterns aren't exhaustive. 2012-02-15 09:40:42 +01:00			`fn test_box() {`
Add `: Box<_>` or `::Box<_>` type annotations to various places. This is the kind of change that one is expected to need to make to accommodate overloaded-`box`. ---- Note that this is not all of the changes necessary to accommodate Issue 22181. It is merely the subset of those cases where there was already a let-binding in place that made it easy to add the necesasry type ascription. (For unnamed intermediate `Box` values, one must go down a different route; `Box::new` is the option that maximizes portability, but has potential inefficiency depending on whether the call is inlined.) ---- There is one place worth note, `run-pass/coerce-match.rs`, where I used an ugly form of `Box<_>` type ascription where I would have preferred to use `Box::new` to accommodate overloaded-`box`. I deliberately did not use `Box::new` here, because that is already done in coerce-match-calls.rs. ---- Precursor for overloaded-`box` and placement-`in`; see Issue 22181. 2015-02-17 21:41:32 +01:00			`let res: Box<_> = match true { true => { box 100 }, _ => panic!() };`
Remove all `i` suffixes 2015-01-25 22:05:03 +01:00			`assert_eq!(*res, 100);`
Rewrite exhaustiveness checker Issue #352 Closes #1720 The old checker would happily accept things like 'alt x { @some(a) { a } }'. It now properly descends into patterns, checks exhaustiveness of booleans, and complains when number/string patterns aren't exhaustive. 2012-02-15 09:40:42 +01:00			`}`
Create a bunch of test cases for unique boxes by copying box tests XFAIL the ones that don't work Issue #409 2011-09-23 14:58:06 -07:00
check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() { test_box(); }`