mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
65f92a52bf
rust/tests/ui/consts/const-extern-fn/const-extern-fn-requires-unsafe.mir.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

20 lines
739 B
Plaintext
Raw Normal View History

Revert "add `DefId` to unsafety violations and display function path in E0133" This reverts commit 8b8f6653cfd54525714f02efe7af0a0f830e185c.
2022-04-26 05:43:00 -05:00
error[E0133]: call to unsafe function is unsafe and requires unsafe function or block
update test Signed-off-by: Miguel Guarniz <mi9uel9@gmail.com>
2022-06-22 11:53:36 -05:00
--> $DIR/const-extern-fn-requires-unsafe.rs:12: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 18:22:18 -05:00
|
update test Signed-off-by: Miguel Guarniz <mi9uel9@gmail.com>
2022-06-22 11:53:36 -05:00
LL | foo();
| ^^^^^ call to unsafe function
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 18:22:18 -05:00
|
= note: consult the function's documentation for information on how to avoid undefined behavior
Revert "add `DefId` to unsafety violations and display function path in E0133" This reverts commit 8b8f6653cfd54525714f02efe7af0a0f830e185c.
2022-04-26 05:43:00 -05:00
error[E0133]: call to unsafe function is unsafe and requires unsafe function or block
update test Signed-off-by: Miguel Guarniz <mi9uel9@gmail.com>
2022-06-22 11:53:36 -05:00
--> $DIR/const-extern-fn-requires-unsafe.rs:9:17
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 18:22:18 -05:00
|
update test Signed-off-by: Miguel Guarniz <mi9uel9@gmail.com>
2022-06-22 11:53:36 -05:00
LL | let a: [u8; foo()];
| ^^^^^ call to unsafe function
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 18:22:18 -05:00
|
= note: consult the function's documentation for information on how to avoid undefined behavior
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0133`.
Reference in New Issue Copy Permalink