rust
/
nomicon
mirror of https://github.com/rust-lang/nomicon
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #294 from JohnTitor/clarify-safe-vs-unsafe-relation

Browse Source 
Clarify the Safe vs. Unsafe Rust relationship
pull/322/head
Eric Huss 3 years ago committed by GitHub
parent b6808de76b e43b81128f
commit 6c2aeef84b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
src/safe-unsafe-meaning.md
Unescape View File

@ -63,7 +63,7 @@ of Safe Rust, the *soundness property*:
The design of the safe/unsafe split means that there is an asymmetric trust The design of the safe/unsafe split means that there is an asymmetric trust
relationship between Safe and Unsafe Rust. Safe Rust inherently has to relationship between Safe and Unsafe Rust. Safe Rust inherently has to
trust that any Unsafe Rust it touches has been written correctly. trust that any Unsafe Rust it touches has been written correctly.
On the other hand, Unsafe Rust has to be very careful about trusting Safe Rust. On the other hand, Unsafe Rust cannot trust Safe Rust without care.
As an example, Rust has the [`PartialOrd`] and [`Ord`] traits to differentiate As an example, Rust has the [`PartialOrd`] and [`Ord`] traits to differentiate
between types which can "just" be compared, and those that provide a "total" between types which can "just" be compared, and those that provide a "total"

Write Preview
Loading…
Cancel
Save