From d6fbd215a15b27be3e28e25c0a1eb71887000971 Mon Sep 17 00:00:00 2001 From: Nabeelimran <31319555+nabeelimran@users.noreply.github.com> Date: Sat, 26 Apr 2025 20:37:10 +0500 Subject: [PATCH] fix: typo in "unsafe external functions" (#2724) --- src/unsafe-rust/unsafe-functions/extern-c.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/unsafe-rust/unsafe-functions/extern-c.md b/src/unsafe-rust/unsafe-functions/extern-c.md index 36b145a3..1af7d435 100644 --- a/src/unsafe-rust/unsafe-functions/extern-c.md +++ b/src/unsafe-rust/unsafe-functions/extern-c.md @@ -33,9 +33,9 @@ fn main() { 1.82 with `unsafe extern` blocks. - `abs` must be explicitly marked as `safe` because it is an external function (FFI). Calling external functions is usually only a problem when those - functions do things with pointers which which might violate Rust's memory - model, but in general any C function might have undefined behaviour under any - arbitrary circumstances. + functions do things with pointers which might violate Rust's memory model, but + in general any C function might have undefined behaviour under any arbitrary + circumstances. - The `"C"` in this example is the ABI; [other ABIs are available too](https://doc.rust-lang.org/reference/items/external-blocks.html). - Note that there is no verification that the Rust function signature matches