rust/tests/ui/cross-crate/const-cross-crate-extern.rs

//@ run-pass
//@ aux-build:cci_const.rs

#![allow(non_upper_case_globals)]
#![allow(unpredictable_function_pointer_comparisons)]

extern crate cci_const;
use cci_const::bar;
static foo: extern "C" fn() = bar;

pub fn main() {
    assert!(foo == bar);
}
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 12:18:55 +00:00			`//@ run-pass`
Inline constants across crates. 2013-03-07 06:30:20 +00:00			`//@ aux-build:cci_const.rs`
Allow fn pointers comparisons lint in UI tests 2023-12-10 14:51:06 +00:00
Add `#![allow(..)]` for a slew of lints of migrated run-pass tests, to silence stderr output. 2018-08-31 13:02:01 +00:00			`#![allow(non_upper_case_globals)]`
Allow fn pointers comparisons lint in UI tests 2023-12-10 14:51:06 +00:00			`#![allow(unpredictable_function_pointer_comparisons)]`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 20:13:15 +00:00
extern mod => extern crate This was previously implemented, and it just needed a snapshot to go through 2014-02-14 18:10:06 +00:00			`extern crate cci_const;`
Inline constants across crates. 2013-03-07 06:30:20 +00:00			`use cci_const::bar;`
Change type of extern fns from `*u8` to `extern "ABI" fn` cc #3678 2013-08-21 13:27:48 +00:00			`static foo: extern "C" fn() = bar;`
Inline constants across crates. 2013-03-07 06:30:20 +00:00
testsuite: more `pub fn main` 2013-03-27 16:58:28 +00:00			`pub fn main() {`
std: Change assert_eq!() to use {} instead of {:?} Formatting via reflection has been a little questionable for some time now, and it's a little unfortunate that one of the standard macros will silently use reflection when you weren't expecting it. This adds small bits of code bloat to libraries, as well as not always being necessary. In light of this information, this commit switches assert_eq!() to using {} in the error message instead of {:?}. In updating existing code, there were a few error cases that I encountered: * It's impossible to define Show for [T, ..N]. I think DST will alleviate this because we can define Show for [T]. * A few types here and there just needed a #[deriving(Show)] * Type parameters needed a Show bound, I often moved this to `assert!(a == b)` * `Path` doesn't implement `Show`, so assert_eq!() cannot be used on two paths. I don't think this is much of a regression though because {:?} on paths looks awful (it's a byte array). Concretely speaking, this shaved 10K off a 656K binary. Not a lot, but sometime significant for smaller binaries. 2014-02-28 09:23:06 +00:00			`assert!(foo == bar);`
Inline constants across crates. 2013-03-07 06:30:20 +00:00			`}`