rust/tests/ui/issues/issue-16560.rs

//@ run-pass
#![allow(unused_variables)]
//@ needs-threads

use std::thread;
use std::mem;

fn main() {
    let y = 0u8;
    let closure = move |x: u8| y + x;

    // Check that both closures are capturing by value
    assert_eq!(1, mem::size_of_val(&closure));

    thread::spawn(move|| {
        let ok = closure;
    }).join().ok().unwrap();
}
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 12:18:55 +00:00			`//@ run-pass`
Add `#![allow(..)]` as necessary to get re-migrated run-pass tests compiling with clean stderr again. Most were added mechanically. 2018-09-25 21:51:35 +00:00			`#![allow(unused_variables)]`
compiletest: Add a `//@ needs-threads` directive This commit is extracted from #122036 and adds a new directive to the `compiletest` test runner, `//@ needs-threads`. This is intended to capture the need that a target must implement threading to execute a specific test, typically one that uses `std::thread`. This is primarily done for WebAssembly targets which currently do not have threads by default. This enables transitioning a lot of `//@ ignore-wasm*`-style ignores into a more self-documenting `//@ needs-threads` directive. Additionally the `wasm32-wasi-preview1-threads` target, for example, does actually have threads, but isn't tested in CI at this time. This change enables running these tests for that target, but not other wasm targets. 2024-03-06 20:19:20 +00:00			`//@ needs-threads`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 20:13:15 +00:00
Test fixes and rebase conflicts 2015-02-17 23:24:34 +00:00			`use std::thread;`
Add test cases for E-needstest issues 2014-10-25 22:07:41 +00:00			`use std::mem;`

			`fn main() {`
			`let y = 0u8;`
Fallout where types must be specified. This is due to a [breaking-change] to operators. The primary affected code is uses of the `Rng` trait where we used to (incorrectly) infer the right-hand-side type from the left-hand-side, in the case that the LHS type was a scalar like `i32`. The fix is to add a type annotation like `x + rng.gen::<i32>()`. 2015-03-24 19:45:11 +00:00			`let closure = move \|x: u8\| y + x;`
Add test cases for E-needstest issues 2014-10-25 22:07:41 +00:00
			`// Check that both closures are capturing by value`
			`assert_eq!(1, mem::size_of_val(&closure));`

Test fixes and rebase conflicts 2015-02-17 23:24:34 +00:00			`thread::spawn(move\|\| {`
Add test cases for E-needstest issues 2014-10-25 22:07:41 +00:00			`let ok = closure;`
std: Stabilize the prelude module This commit is an implementation of [RFC 503][rfc] which is a stabilization story for the prelude. Most of the RFC was directly applied, removing reexports. Some reexports are kept around, however: * `range` remains until range syntax has landed to reduce churn. * `Path` and `GenericPath` remain until path reform lands. This is done to prevent many imports of `GenericPath` which will soon be removed. * All `io` traits remain until I/O reform lands so imports can be rewritten all at once to `std::io::prelude::*`. This is a breaking change because many prelude reexports have been removed, and the RFC can be consulted for the exact list of removed reexports, as well as to find the locations of where to import them. [rfc]: https://github.com/rust-lang/rfcs/blob/master/text/0503-prelude-stabilization.md [breaking-change] Closes #20068 2014-12-22 17:04:23 +00:00			`}).join().ok().unwrap();`
Add test cases for E-needstest issues 2014-10-25 22:07:41 +00:00			`}`