rust/tests/ui/extern-mod-syntax.rs

// run-pass

#![allow(unused_imports)]
#![no_std]

extern crate std;
use std::ffi::c_void;

pub fn main() {
    std::println!("Hello world!");
}
tests: Add missing run-pass annotations 2019-07-26 16:54:25 -05:00			`// run-pass`

Use new attribute syntax in python files in src/etc too (#13478) 2014-04-14 10:30:31 -05:00			`#![allow(unused_imports)]`
Fix tests on wasm The `std` test straightforwardly can't work without file descriptors; #99417 tracks moving it out of tests/ui. `issue-13560.rs` requires the target to support dynamic linking. `extern-mod-syntax` is interesting. The original test was added to check if `extern mod` could be parsed correctly and used `extern mod std` and an import: https://github.com/rust-lang/rust/commit/138dc3048af36f0a20f857542c357fe8df563013#diff-73700e1e851b7a37bc92174635dab726124c82e5bfabbbc45b4a3c2e8e14fadd At some point `std::json::Object` was moved out of std to an unstable rustc-only `extras` crate, and rather than just changing the import it got changed to use the unstable crate. When `extras` was removed, people assumed the test was meant to also test rustc_private and changed it to another unstable crate rather than using something in std. This changes the test to remove the `rustc_private` import, to allow it to work properly when cross-compiling. 2023-04-09 09:11:00 -05:00			`#![no_std]`
Fix warnings it tests 2013-08-17 10:37:42 -05:00
Fix tests on wasm The `std` test straightforwardly can't work without file descriptors; #99417 tracks moving it out of tests/ui. `issue-13560.rs` requires the target to support dynamic linking. `extern-mod-syntax` is interesting. The original test was added to check if `extern mod` could be parsed correctly and used `extern mod std` and an import: https://github.com/rust-lang/rust/commit/138dc3048af36f0a20f857542c357fe8df563013#diff-73700e1e851b7a37bc92174635dab726124c82e5bfabbbc45b4a3c2e8e14fadd At some point `std::json::Object` was moved out of std to an unstable rustc-only `extras` crate, and rather than just changing the import it got changed to use the unstable crate. When `extras` was removed, people assumed the test was meant to also test rustc_private and changed it to another unstable crate rather than using something in std. This changes the test to remove the `rustc_private` import, to allow it to work properly when cross-compiling. 2023-04-09 09:11:00 -05:00			`extern crate std;`
			`use std::ffi::c_void;`
libsyntax: Parse "extern mod foo;" 2012-08-14 16:22:52 -05:00
check-fast fallout from removing export, r=burningtree 2013-02-01 21:43:17 -06:00			`pub fn main() {`
Fix tests on wasm The `std` test straightforwardly can't work without file descriptors; #99417 tracks moving it out of tests/ui. `issue-13560.rs` requires the target to support dynamic linking. `extern-mod-syntax` is interesting. The original test was added to check if `extern mod` could be parsed correctly and used `extern mod std` and an import: https://github.com/rust-lang/rust/commit/138dc3048af36f0a20f857542c357fe8df563013#diff-73700e1e851b7a37bc92174635dab726124c82e5bfabbbc45b4a3c2e8e14fadd At some point `std::json::Object` was moved out of std to an unstable rustc-only `extras` crate, and rather than just changing the import it got changed to use the unstable crate. When `extras` was removed, people assumed the test was meant to also test rustc_private and changed it to another unstable crate rather than using something in std. This changes the test to remove the `rustc_private` import, to allow it to work properly when cross-compiling. 2023-04-09 09:11:00 -05:00			`std::println!("Hello world!");`
libsyntax: Parse "extern mod foo;" 2012-08-14 16:22:52 -05:00			`}`