rust/tests/ui/pattern/pattern-match-arc-move.rs

//! Tests moving an `Arc` value out of an `Option` in a match expression.

//@ run-pass

use std::sync::Arc;
fn dispose(_x: Arc<bool>) { }

pub fn main() {
    let p = Arc::new(true);
    let x = Some(p);
    match x {
        Some(z) => { dispose(z); },
        None => panic!()
    }
}
cleaned up some tests 2025-06-01 00:03:54 +05:00			//! Tests moving an `Arc` value out of an `Option` in a match expression.

tests: Add missing run-pass annotations 2019-07-27 00:54:25 +03:00			`//@ run-pass`

sync: Move underneath libstd This commit is the final step in the libstd facade, #13851. The purpose of this commit is to move libsync underneath the standard library, behind the facade. This will allow core primitives like channels, queues, and atomics to all live in the same location. There were a few notable changes and a few breaking changes as part of this movement: * The `Vec` and `String` types are reexported at the top level of libcollections * The `unreachable!()` macro was copied to libcore * The `std::rt::thread` module was moved to librustrt, but it is still reexported at the same location. * The `std::comm` module was moved to libsync * The `sync::comm` module was moved under `sync::comm`, and renamed to `duplex`. It is now a private module with types/functions being reexported under `sync::comm`. This is a breaking change for any existing users of duplex streams. * All concurrent queues/deques were moved directly under libsync. They are also all marked with #![experimental] for now if they are public. * The `task_pool` and `future` modules no longer live in libsync, but rather live under `std::sync`. They will forever live at this location, but they may move to libsync if the `std::task` module moves as well. [breaking-change] 2014-06-07 11:13:26 -07:00			`use std::sync::Arc;`
move concurrent stuff from libextra to libsync 2014-01-30 15:04:47 -05:00			`fn dispose(_x: Arc<bool>) { }`
WIP: Add an xfailed test for bind-by-move (#2329) 2012-08-22 20:37:59 -04:00
check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() {`
move concurrent stuff from libextra to libsync 2014-01-30 15:04:47 -05:00			`let p = Arc::new(true);`
Fix Option camel case in xfailed/ignored tests 2013-01-25 12:31:45 -07:00			`let x = Some(p);`
tests/tutorials: Get rid of `move`. 2013-02-15 02:44:18 -08:00			`match x {`
			`Some(z) => { dispose(z); },`
Rename fail! to panic! 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-09 15:17:22 -04:00			`None => panic!()`
WIP: Add an xfailed test for bind-by-move (#2329) 2012-08-22 20:37:59 -04:00			`}`
			`}`