From dc77c2e2cb3cbf0f52c57930dfea9478df6637ab Mon Sep 17 00:00:00 2001 From: Martin Geisler Date: Sat, 31 Jan 2026 13:04:49 +0100 Subject: [PATCH] tuples-and-arrays: remove weasel words (#3043) This PR removes imprecise language ('weasel words') to align with the new precision guidelines in #3029. --- *Note: This PR was generated using Gemini. Please review the changes accordingly. If the new style is not desired for this section, feel free to close this PR.* --- src/tuples-and-arrays/arrays.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/tuples-and-arrays/arrays.md b/src/tuples-and-arrays/arrays.md index 7ed8b387..eaee3463 100644 --- a/src/tuples-and-arrays/arrays.md +++ b/src/tuples-and-arrays/arrays.md @@ -37,8 +37,8 @@ fn main() { } ``` -- Array accesses are checked at runtime. Rust can usually optimize these checks - away; meaning if the compiler can prove the access is safe, it removes the +- Array accesses are checked at runtime. Rust optimizes these checks away when + possible; meaning if the compiler can prove the access is safe, it removes the runtime check for better performance. They can be avoided using unsafe Rust. The optimization is so good that it's hard to give an example of runtime checks failing. The following code will compile but panic at runtime: