9e3d0b002a
This breaks a fair amount of code. The typical patterns are:
* `for _ in range(0, 10)`: change to `for _ in range(0u, 10)`;
* `println!("{}", 3)`: change to `println!("{}", 3i)`;
* `[1, 2, 3].len()`: change to `[1i, 2, 3].len()`.
RFC #30. Closes #6023.
[breaking-change]
35 lines
1.1 KiB
Rust
35 lines
1.1 KiB
Rust
// Copyright 2013-2014 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.
|
|
|
|
|
|
// aux-build:trait_superkinds_in_metadata.rs
|
|
|
|
// Tests "capabilities" granted by traits with super-builtin-kinds,
|
|
// even when using them cross-crate.
|
|
|
|
extern crate trait_superkinds_in_metadata;
|
|
use trait_superkinds_in_metadata::{RequiresRequiresShareAndSend, RequiresShare};
|
|
|
|
#[deriving(PartialEq)]
|
|
struct X<T>(T);
|
|
|
|
impl <T: Share> RequiresShare for X<T> { }
|
|
impl <T: Share+Send> RequiresRequiresShareAndSend for X<T> { }
|
|
|
|
fn foo<T: RequiresRequiresShareAndSend>(val: T, chan: Sender<T>) {
|
|
chan.send(val);
|
|
}
|
|
|
|
pub fn main() {
|
|
let (tx, rx): (Sender<X<int>>, Receiver<X<int>>) = channel();
|
|
foo(X(31337i), tx);
|
|
assert!(rx.recv() == X(31337i));
|
|
}
|