Skip to content

Commit 1cef026

Browse files
committed
Improve wording of where safe is allowed
Let's improve the wording related to where the `safe` keyword is allowed. (Thanks to Waffle for raising this point.)
1 parent 23f0acf commit 1cef026

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

text/0000-unsafe-extern-blocks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ An extern static value is also declared with a `;` instead of an expression (sim
3333
In both cases, the actual function body or value is provided by whatever external source (which is probably not even written in Rust).
3434

3535
When an `unsafe extern` block is used, all declarations within that `extern` block *must* have the `unsafe` or `safe` keywords as part of their signature.
36-
The `safe` keyword is a contextual keyword, it is currently only used within `extern` blocks.
36+
The `safe` keyword is a contextual keyword; it is currently allowed only within `extern` blocks.
3737

3838
If an `extern` block is used in an older edition without the `unsafe` keyword, declarations *cannot* specify `safe` or `unsafe`.
3939
Code must update to `unsafe extern` style blocks if it wants to make `safe` declarations.

0 commit comments

Comments
 (0)