granite-rust/tests/ui/parser/no-const-fn-in-extern-block.rs

extern "C" {
    const fn foo();
    //~^ ERROR functions in `extern` blocks cannot
    const unsafe fn bar();
    //~^ ERROR functions in `extern` blocks cannot
    //~| ERROR items in `extern` blocks without an `unsafe` qualifier cannot
}

fn main() {}
Update tests for extern block linting 2020-09-01 17:12:52 -04:00			`extern "C" {`
Add support for 'extern const fn' This works just as you might expect - an 'extern const fn' is a 'const fn' that is callable from foreign code. Currently, panicking is not allowed in consts. When RFC 2345 is stabilized, then panicking in an 'extern const fn' will produce a compile-time error when invoked at compile time, and an abort when invoked at runtime. Since this is extending the language (we're allowing the `const` keyword in a new context), I believe that this will need an FCP. However, it's a very minor change, so I didn't think that filing an RFC was necessary. This will allow libc (and other FFI crates) to make many functions `const`, without having to give up on making them `extern` as well. 2019-09-29 19:22:18 -04:00			`const fn foo();`
Note what qualifier 2024-10-11 11:30:03 -04:00			//~^ ERROR functions in `extern` blocks cannot
Add support for 'extern const fn' This works just as you might expect - an 'extern const fn' is a 'const fn' that is callable from foreign code. Currently, panicking is not allowed in consts. When RFC 2345 is stabilized, then panicking in an 'extern const fn' will produce a compile-time error when invoked at compile time, and an abort when invoked at runtime. Since this is extending the language (we're allowing the `const` keyword in a new context), I believe that this will need an FCP. However, it's a very minor change, so I didn't think that filing an RFC was necessary. This will allow libc (and other FFI crates) to make many functions `const`, without having to give up on making them `extern` as well. 2019-09-29 19:22:18 -04:00			`const unsafe fn bar();`
Note what qualifier 2024-10-11 11:30:03 -04:00			//~^ ERROR functions in `extern` blocks cannot
			//~\| ERROR items in `extern` blocks without an `unsafe` qualifier cannot
Add support for 'extern const fn' This works just as you might expect - an 'extern const fn' is a 'const fn' that is callable from foreign code. Currently, panicking is not allowed in consts. When RFC 2345 is stabilized, then panicking in an 'extern const fn' will produce a compile-time error when invoked at compile time, and an abort when invoked at runtime. Since this is extending the language (we're allowing the `const` keyword in a new context), I believe that this will need an FCP. However, it's a very minor change, so I didn't think that filing an RFC was necessary. This will allow libc (and other FFI crates) to make many functions `const`, without having to give up on making them `extern` as well. 2019-09-29 19:22:18 -04:00			`}`

			`fn main() {}`