os-rust/tests/ui/issues/issue-2723-b.rs

//@ run-pass
//@ aux-build:issue-2723-a.rs

extern crate issue_2723_a;
use issue_2723_a::f;

pub fn main() {
    unsafe {
        f(vec![2]);
    }
}
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 14:18:55 +02:00			`//@ run-pass`
Moved issue tests to subdirs and normalised names. 2019-03-12 00:49:17 +00:00			`//@ aux-build:issue-2723-a.rs`
Test for #2723. Closes #2723 2012-07-11 12:33:55 -07:00
extern mod => extern crate This was previously implemented, and it just needed a snapshot to go through 2014-02-14 10:10:06 -08:00			`extern crate issue_2723_a;`
Add appropriate #[feature] directives to tests 2013-10-02 20:00:54 -07:00			`use issue_2723_a::f;`
Test for #2723. Closes #2723 2012-07-11 12:33:55 -07:00
check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() {`
libsyntax: Remove `fn() unsafe { ... }`. r=graydon 2013-01-23 11:43:58 -08:00			`unsafe {`
Changed most vec! invocations to use square braces Most of the Rust community agrees that the vec! macro is clearer when called using square brackets [] instead of regular brackets (). Most of these ocurrences are from before macros allowed using different types of brackets. There is one left unchanged in a pretty-print test, as the pretty printer still wants it to have regular brackets. 2016-10-29 22:54:04 +01:00			`f(vec![2]);`
libsyntax: Remove `fn() unsafe { ... }`. r=graydon 2013-01-23 11:43:58 -08:00			`}`
			`}`