Skip to content

Commit e1efa5c

Browse files
authored
Fix typo.
1 parent c9da2db commit e1efa5c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/2025h1/safe-linking.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Specifically, figure out how it'd be possible to provide any kind of safety when
1616
Rust has a very clear definition of "safe" and "unsafe" and (usually) makes it easy to stay in the "safe" world.
1717
`unsafe` blocks usually only have to encapsulate very small blocks of which one can (and should) prove soundness manually.
1818

19-
When using `#[no_mangle]` and/or `extern { … }` to connect separately compiled code, however, any concept safety pretty much disappears.
19+
When using `#[no_mangle]` and/or `extern { … }` to connect separately compiled code, however, any concept of safety pretty much disappears.
2020

2121
While it might be reasonable to make some assumptions about (standardized) symbols like `strlen`,
2222
the _unsafe assumption_ that a symbol with the same name will refer to something of the expected signature

0 commit comments

Comments
 (0)