From e43b81128f37c4896f7e9bf36433d9eaa471c8c1 Mon Sep 17 00:00:00 2001 From: Yuki Okushi Date: Wed, 28 Jul 2021 04:48:56 +0900 Subject: [PATCH] Clarify the Safe vs. Unsafe Rust relationship --- src/safe-unsafe-meaning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/safe-unsafe-meaning.md b/src/safe-unsafe-meaning.md index 6f55622e..f7cd68cf 100644 --- a/src/safe-unsafe-meaning.md +++ b/src/safe-unsafe-meaning.md @@ -63,7 +63,7 @@ of Safe Rust, the *soundness property*: 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 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 between types which can "just" be compared, and those that provide a "total"