270f0eef73
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.
32 lines
898 B
Rust
32 lines
898 B
Rust
// Copyright 2012 The Rust Project Developers. See the COPYRIGHT
|
|
// file at the top-level directory of this distribution and at
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
// option. This file may not be copied, modified, or distributed
|
|
// except according to those terms.
|
|
|
|
#![allow(unknown_features)]
|
|
#![feature(box_syntax)]
|
|
|
|
use std::thread;
|
|
|
|
pub fn main() { test05(); }
|
|
|
|
fn test05_start<F:FnOnce(int)>(f: F) {
|
|
f(22);
|
|
}
|
|
|
|
fn test05() {
|
|
let three: Box<_> = box 3;
|
|
let fn_to_send = move|n:int| {
|
|
println!("{}", *three + n); // will copy x into the closure
|
|
assert_eq!(*three, 3);
|
|
};
|
|
thread::spawn(move|| {
|
|
test05_start(fn_to_send);
|
|
}).join().ok().unwrap();
|
|
}
|