mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Rollup merge of #112037 - Nemo157:e0133-unsafe_op_in_unsafe_fn, r=petrochenkov

Browse Source 
Add details about `unsafe_op_in_unsafe_fn` to E0133

This was mentioned in https://github.com/rust-lang/rust/pull/99827#discussion_r933899901
This commit is contained in:
Matthias Krüger 2023-05-29 04:03:02 +02:00 committed by GitHub
commit c5a93ba9fe
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
compiler/rustc_error_codes/src/error_codes/E0133.md
View File

@ -1,4 +1,4 @@
Unsafe code was used outside of an unsafe function or block. Unsafe code was used outside of an unsafe block.
Erroneous code example: Erroneous code example:
@ -30,4 +30,21 @@ fn main() {
See the [unsafe section][unsafe-section] of the Book for more details. See the [unsafe section][unsafe-section] of the Book for more details.
#### Unsafe code in functions
Unsafe code is currently accepted in unsafe functions, but that is being phased
out in favor of requiring unsafe blocks here too.
```
unsafe fn f() { return; }
unsafe fn g() {
f(); // Is accepted, but no longer recommended
unsafe { f(); } // Recommended way to write this
}
```
Linting against this is controlled via the `unsafe_op_in_unsafe_fn` lint, which
is `allow` by default but will be upgraded to `warn` in a future edition.
[unsafe-section]: https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html [unsafe-section]: https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html