granite-rust/tests/ui/consts/const-extern-function.rs

// run-pass
#![allow(non_upper_case_globals)]

extern "C" fn foopy() {}

static f: extern "C" fn() = foopy;
static s: S = S { f: foopy };

struct S {
    f: extern "C" fn()
}

pub fn main() {
    assert!(foopy as extern "C" fn() == f);
    assert!(f == s.f);
}
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`
Add `#![allow(..)]` for a slew of lints of migrated run-pass tests, to silence stderr output. 2018-08-31 15:02:01 +02:00			`#![allow(non_upper_case_globals)]`
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 13:13:15 -07:00
Update code to account for extern ABI requirement 2020-09-01 17:28:11 -04:00			`extern "C" fn foopy() {}`
Translate const references to extern functions as *i8 instead of the typical closure pair. Fixes #4522. 2013-01-18 16:12:07 +01:00
Change type of extern fns from `*u8` to `extern "ABI" fn` cc #3678 2013-08-21 09:27:48 -04:00			`static f: extern "C" fn() = foopy;`
librustc: Remove the `const` declaration form everywhere 2013-03-22 14:00:15 -07:00			`static s: S = S { f: foopy };`
Translate const references to extern functions as *i8 instead of the typical closure pair. Fixes #4522. 2013-01-18 16:12:07 +01:00
			`struct S {`
Change type of extern fns from `*u8` to `extern "ABI" fn` cc #3678 2013-08-21 09:27:48 -04:00			`f: extern "C" fn()`
Translate const references to extern functions as *i8 instead of the typical closure pair. Fixes #4522. 2013-01-18 16:12:07 +01:00			`}`

check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() {`
Fix fallout from changes. In cases where stage0 compiler is needed, we cannot use an `as` expression to coerce, so I used a one-off function instead (this is a no-op in stage0, but in stage1+ it triggers coercion from the fn pointer to the fn item type). 2014-11-26 05:52:16 -05:00			`assert!(foopy as extern "C" fn() == f);`
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 01:23:06 -08:00			`assert!(f == s.f);`
librustc: Replace `impl Type : Trait` with `impl Trait for Type`. rs=implflipping 2013-02-14 11:47:00 -08:00			`}`