Skip to content

Commit 676383f

Browse files
Update text/0000-unsafe-extern-blocks.md
Co-authored-by: Jacob Lifshay <[email protected]>
1 parent 2144ac3 commit 676383f

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

text/0000-unsafe-extern-blocks.md

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

3636
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.
37-
If one of the two keywords is not explicitly provided, the declaration is assumed to be `unsafe`, and also a warning is generated.
3837
The `safe` keyword is a contextual keyword, it is currently only used within `extern` blocks.
3938

4039
If an `extern` block is used in an older edition without the `unsafe` keyword, declarations *cannot* specify `safe` or `unsafe`.

0 commit comments

Comments
 (0)