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

error: functions in `extern` blocks cannot have `const` qualifier
  --> $DIR/no-const-fn-in-extern-block.rs:2:5
   |
LL | extern "C" {
   | ---------- in this `extern` block
LL |     const fn foo();
   |     ^^^^^ help: remove the `const` qualifier

error: functions in `extern` blocks cannot have `const` qualifier
  --> $DIR/no-const-fn-in-extern-block.rs:4:5
   |
LL | extern "C" {
   | ---------- in this `extern` block
...
LL |     const unsafe fn bar();
   |     ^^^^^ help: remove the `const` qualifier

error: items in `extern` blocks without an `unsafe` qualifier cannot have safety qualifiers
  --> $DIR/no-const-fn-in-extern-block.rs:4:5
   |
LL |     const unsafe fn bar();
   |     ^^^^^^^^^^^^^^^^^^^^^^
   |
help: add `unsafe` to this `extern` block
   |
LL | unsafe extern "C" {
   | ++++++

error: aborting due to 3 previous errors
Note what qualifier 2024-10-11 11:30:03 -04:00			error: functions in `extern` blocks cannot have `const` qualifier
Fix diagnostic for qualifier in extern block Closes: https://github.com/rust-lang/rust/issues/123306 2024-04-03 02:43:54 +02:00			`--> $DIR/no-const-fn-in-extern-block.rs:2:5`
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			`\|`
Update tests for extern block linting 2020-09-01 17:12:52 -04:00			`LL \| extern "C" {`
			\| ---------- in this `extern` block
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			`LL \| const fn foo();`
Note what qualifier 2024-10-11 11:30:03 -04:00			\| ^^^^^ help: remove the `const` qualifier
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
Note what qualifier 2024-10-11 11:30:03 -04:00			error: functions in `extern` blocks cannot have `const` qualifier
Fail when using safe/unsafe items inside unadorned extern blocks 2024-05-27 15:35:34 -03:00			`--> $DIR/no-const-fn-in-extern-block.rs:4:5`
			`\|`
			`LL \| extern "C" {`
Do not allow safe usafe on static and fn items 2024-06-20 16:19:43 -03:00			\| ---------- in this `extern` block
Fail when using safe/unsafe items inside unadorned extern blocks 2024-05-27 15:35:34 -03:00			`...`
			`LL \| const unsafe fn bar();`
Note what qualifier 2024-10-11 11:30:03 -04:00			\| ^^^^^ help: remove the `const` qualifier
Fail when using safe/unsafe items inside unadorned extern blocks 2024-05-27 15:35:34 -03:00
Remove unadorned 2024-10-11 11:24:14 -04:00			error: items in `extern` blocks without an `unsafe` qualifier cannot have safety qualifiers
Fix diagnostic for qualifier in extern block Closes: https://github.com/rust-lang/rust/issues/123306 2024-04-03 02:43:54 +02:00			`--> $DIR/no-const-fn-in-extern-block.rs:4:5`
Fix ui tests for `fn`s with qualifiers in `extern` blocks 2020-11-15 15:34:51 -06:00			`\|`
Fix diagnostic for qualifier in extern block Closes: https://github.com/rust-lang/rust/issues/123306 2024-04-03 02:43:54 +02:00			`LL \| const unsafe fn bar();`
Do not allow safe usafe on static and fn items 2024-06-20 16:19:43 -03:00			`\| ^^^^^^^^^^^^^^^^^^^^^^`
Fix bad replacement for unsafe extern block suggestion 2024-06-26 08:44:59 +08:00			`\|`
Remove unadorned 2024-10-11 11:24:14 -04:00			help: add `unsafe` to this `extern` block
Fix bad replacement for unsafe extern block suggestion 2024-06-26 08:44:59 +08:00			`\|`
			`LL \| unsafe 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
Fail when using safe/unsafe items inside unadorned extern blocks 2024-05-27 15:35:34 -03:00			`error: aborting due to 3 previous errors`
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