add const_fn features

This commit is contained in:
Niko Matsakis 2015-05-29 09:42:32 -04:00
parent 1f29fd4eb0
commit 2c5e784d6f
27 changed files with 38 additions and 1 deletions

View File

@ -14,6 +14,7 @@
#![feature(collections)]
#![feature(collections_drain)]
#![feature(core)]
#![feature(const_fn)]
#![feature(hash)]
#![feature(rand)]
#![feature(rustc_private)]

View File

@ -14,6 +14,7 @@
#![feature(box_syntax)]
#![feature(unboxed_closures)]
#![feature(core)]
#![feature(const_fn)]
#![feature(test)]
#![feature(rand)]
#![feature(unicode)]

View File

@ -173,6 +173,7 @@
#![feature(staged_api)]
#![feature(box_syntax)]
#![feature(core)]
#![feature(const_fn)]
#![feature(std_misc)]
use std::boxed;

View File

@ -29,6 +29,7 @@
#![feature(box_patterns)]
#![feature(box_syntax)]
#![feature(collections)]
#![feature(const_fn)]
#![feature(core)]
#![feature(duration)]
#![feature(duration_span)]

View File

@ -30,6 +30,7 @@
#![feature(box_syntax)]
#![feature(collections)]
#![feature(core)]
#![feature(const_fn)]
#![feature(libc)]
#![feature(quote)]
#![feature(rustc_diagnostic_macros)]

View File

@ -8,6 +8,8 @@
// option. This file may not be copied, modified, or distributed
// except according to those terms.
#![feature(const_fn)]
use std::sync::atomic;
pub const C1: usize = 1;

View File

@ -13,6 +13,8 @@
//
// (Compare against compile-fail/dropck_vec_cycle_checked.rs)
#![feature(const_fn)]
use std::cell::Cell;
use id::Id;

View File

@ -17,6 +17,7 @@
// for the error message we see here.)
#![allow(unstable)]
#![feature(const_fn)]
extern crate arena;

View File

@ -13,6 +13,8 @@
//
// (Compare against compile-fail/dropck_vec_cycle_checked.rs)
#![feature(const_fn)]
use std::cell::Cell;
use id::Id;

View File

@ -12,6 +12,8 @@
//
// (Compare against compile-fail/dropck_arr_cycle_checked.rs)
#![feature(const_fn)]
use std::cell::Cell;
use id::Id;

View File

@ -10,6 +10,8 @@
// RFC 736 (and Issue 21407): functional struct update should respect privacy.
#![feature(const_fn)]
// The `foo` module attempts to maintains an invariant that each `S`
// has a unique `u64` id.
use self::foo::S;

View File

@ -8,6 +8,8 @@
// option. This file may not be copied, modified, or distributed
// except according to those terms.
#![feature(const_fn)]
use std::cell::UnsafeCell;
const A: UnsafeCell<usize> = UnsafeCell::new(1);

View File

@ -9,6 +9,7 @@
// except according to those terms.
#![feature(box_syntax)]
#![feature(const_fn)]
use std::cell::RefCell;

View File

@ -23,6 +23,8 @@
// conditions above to be satisfied, meaning that if the dropck is
// sound, it should reject this code.
#![feature(const_fn)]
use std::cell::Cell;
use id::Id;

View File

@ -15,6 +15,7 @@
#![allow(dead_code, unused_variables)]
#![omit_gdb_pretty_printer_section]
#![feature(std_misc, core)]
#![feature(const_fn)]
// This test makes sure that the compiler doesn't crash when trying to assign
// debug locations to const-expressions.

View File

@ -9,6 +9,7 @@
// except according to those terms.
#![allow(dead_code)]
#![feature(const_fn)]
// check dtor calling order when casting enums.

View File

@ -12,6 +12,8 @@
// `Item` originates in a where-clause, not the declaration of
// `T`. Issue #20300.
#![feature(const_fn)]
use std::marker::{PhantomData};
use std::sync::atomic::{AtomicUsize};
use std::sync::atomic::Ordering::SeqCst;

View File

@ -11,6 +11,8 @@
// Test that we cleanup a fixed size Box<[D; k]> properly when D has a
// destructor.
#![feature(const_fn)]
use std::thread;
use std::sync::atomic::{AtomicUsize, Ordering};

View File

@ -11,6 +11,8 @@
// Test that we cleanup dynamic sized Box<[D]> properly when D has a
// destructor.
#![feature(const_fn)]
use std::thread;
use std::sync::atomic::{AtomicUsize, Ordering};

View File

@ -10,7 +10,7 @@
#![feature(const_fn)]
struct Foo { val: u32 }
struct Foo { value: u32 }
impl Foo {
const fn new() -> Foo {

View File

@ -11,6 +11,8 @@
// pretty-expanded FIXME #23616
#![feature(core)]
#![feature(const_fn)]
use std::marker;
use std::cell::UnsafeCell;

View File

@ -12,6 +12,7 @@
#![feature(core)]
#![feature(const_fn)]
extern crate issue_17718 as other;

View File

@ -12,6 +12,7 @@
// created via FRU and control-flow breaks in the middle of
// construction.
#![feature(const_fn)]
use std::sync::atomic::{Ordering, AtomicUsize};

View File

@ -12,6 +12,7 @@
// the contents implement Drop and we hit a panic in the middle of
// construction.
#![feature(const_fn)]
use std::thread;
use std::sync::atomic::{AtomicUsize, Ordering};

View File

@ -11,6 +11,7 @@
// Checks that functional-record-update order-of-eval is as expected
// even when no Drop-implementations are involved.
#![feature(const_fn)]
use std::sync::atomic::{Ordering, AtomicUsize};

View File

@ -11,6 +11,7 @@
// Checks that struct-literal expression order-of-eval is as expected
// even when no Drop-implementations are involved.
#![feature(const_fn)]
use std::sync::atomic::{Ordering, AtomicUsize};

View File

@ -10,6 +10,7 @@
#![feature(rand, core)]
#![feature(const_fn)]
use std::sync::atomic::{AtomicUsize, Ordering};
use std::__rand::{thread_rng, Rng};