rust/comprehensive-rust
1
0
Fork 0
mirror of https://github.com/google/comprehensive-rust.git synced 2025-08-08 08:22:52 +02:00
Code Issues Releases Activity

Fix missing link (fixes #2822) (#2823)

Browse Source 
This change fixes a broken link when markdown source is rendered as HTML
by mdbook.
This commit is contained in:
Tim McNamara
2025-07-18 21:48:46 +12:00
committed by GitHub
parent c15f398c3d
commit 8994e390af
1 changed files with 7 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
src/unsafe-deep-dive/motivations/interop.md
View File

@ -51,15 +51,16 @@ parsing all take energy and time.
rely on its symbols, including `random`, being available to our program.
- _What is the "safe" keyword?_\
It allows callers to call the function without needing to wrap that call in
`unsafe`. The [`safe` function qualifier] was introduced in the 2024 edition
of Rust and can only be used within `extern` blocks. It was introduced because
`unsafe` became a mandatory qualifier for `extern` blocks in that edition.
`unsafe`. The [`safe` function qualifier][safe] was introduced in the 2024
edition of Rust and can only be used within `extern` blocks. It was introduced
because `unsafe` became a mandatory qualifier for `extern` blocks in that
edition.
- _What is the [`std::ffi::c_long`] type?_\
According to the C standard, an integer that's at least 32 bits wide. On
today's systems, It's an `i32` on Windows and an `i64` on Linux.
[`safe` keyword]: https://doc.rust-lang.org/reference/safe-keyword.html
[`std::ffi::c_long`]: https://doc.rust-lang.org/std/ffi/type.c_long.html
[safe]: https://doc.rust-lang.org/stable/edition-guide/rust-2024/unsafe-extern.html
## Consideration: type safety
@ -203,15 +204,12 @@ fn main() {
}
```
> Aside: Lifetimes in the `format_timestamp()` function
> _Aside:_ Lifetimes in the `format_timestamp()` function
>
> Neither `'a`, nor `'static` correctly describe the lifetime of the string
> Neither `'a`, nor `'static`, correctly describe the lifetime of the string
> that's returned. Rust treats it as an immutable reference, but subsequent
> calls to `ctime` will overwrite the static buffer that the string occupies.
Bonus points: can anyone spot the lifetime bug? `format_timestamp()` should
return a `&'static str`.
## Consideration: Representation mismatch
Different programming languages have made different design decisions and this