From 7a46f88495bed42275496632329851bda680ef28 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Le=C3=B3n=20Orell=20Valerian=20Liehr?= Date: Thu, 3 Oct 2024 11:31:43 +0200 Subject: [PATCH] Rename "object safe" to "dyn compatible" (#2083) --- src/traits/unsize.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/traits/unsize.md b/src/traits/unsize.md index 4876bfd07..dd57a1b07 100644 --- a/src/traits/unsize.md +++ b/src/traits/unsize.md @@ -16,7 +16,7 @@ pointers, and there are rules about when a type is allowed to implement # [`Unsize`](https://doc.rust-lang.org/std/marker/trait.Unsize.html) To contrast, the `Unsize` trait is concerned the actual types that are allowed -to be unsized. +to be unsized. This is not intended to be implemented by users ever, since `Unsize` does not instruct the compiler (namely codegen) *how* to unsize a type, just whether it @@ -27,7 +27,7 @@ which must understand how types are represented and unsized. Built-in implementations are provided for: * `T` -> `dyn Trait + 'a` when `T: Trait` (and `T: Sized + 'a`, and `Trait` - is object safe). + is dyn-compatible[^2]). * `[T; N]` -> `[T]` ## Structural implementations @@ -82,4 +82,4 @@ Specifically, (3.) prevents a choice of projection bound to guide inference unnecessarily, though it may guide inference when it is unambiguous. [^1]: The principal is the one non-auto trait of a `dyn Trait`. - +[^2]: Formerly known as "object safe".