You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: text/0000-unsafe-extern-blocks.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ unsafe extern {
60
60
Once they are unsafely declared, a `safe` item can be used outside the `extern` block as if it were any other safe function or static value declared within rust.
61
61
The unsafe obligation of ensuring that the correct items are being linked to is performed by the crate making the declaration, not the crate using of that declaration.
62
62
63
-
Items declared as `unsafe`*must* still have a correctly matching signature at compile time, but they *also* some sort of additional obligation for correct usage at runtime.
63
+
Items declared as `unsafe`*must* still have a correctly matching signature at compile time, but they *also*have some sort of additional obligation for correct usage at runtime.
0 commit comments