rust/tests/ui/consts/const-fn-stability-calls-3.rs

// Test use of const fn from another crate without a feature gate.

// check-pass
// aux-build:const_fn_lib.rs

extern crate const_fn_lib;

use const_fn_lib::foo;

fn main() {
    let x = foo(); // use outside a constant is ok
}
New tests for cross-crate usages of const fn and so forth 2015-05-29 08:57:36 -05:00			`// Test use of const fn from another crate without a feature gate.`

compiletest: Remove `skip-codegen` 2019-06-12 10:18:32 -05:00			`// check-pass`
New tests for cross-crate usages of const fn and so forth 2015-05-29 08:57:36 -05:00			`// aux-build:const_fn_lib.rs`

			`extern crate const_fn_lib;`

			`use const_fn_lib::foo;`

Removed `#[rustc_error]` from tests that are all `// compile-pass`. I also added `// skip-codegen` to each one, to address potential concerns that this change would otherwise slow down our test suite spending time generating code for files that are really just meant to be checks of compiler diagnostics. (However, I will say: My preference is to not use `// skip-codegen` if one can avoid it. We can use all the testing of how we drive LLVM that we can get...) (Updated post rebase.) 2018-10-31 07:08:01 -05:00			`fn main() {`
New tests for cross-crate usages of const fn and so forth 2015-05-29 08:57:36 -05:00			`let x = foo(); // use outside a constant is ok`
			`}`