From 378fa89a544596b1be8b434d4b6dae7400a463ce Mon Sep 17 00:00:00 2001 From: Travis Cross Date: Fri, 15 Aug 2025 04:50:08 +0000 Subject: [PATCH] Fix indentation of static path restriction text In the const eval chapter, we have a list of kinds of expressions that are allowed. Paths to statics are one kind that is allowed, but have certain restrictions we describe in bullet points. We then have text that clarifies when these bullet points are checked. This text was outdented beyond the relevant item, which broke up the outer bullet point list and created (momentary) ambiguity about the scope of the rules the language might be affecting. Let's fix that. --- src/const_eval.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/const_eval.md b/src/const_eval.md index 0b89affc7..ae4b3b682 100644 --- a/src/const_eval.md +++ b/src/const_eval.md @@ -46,7 +46,7 @@ r[const-eval.const-expr.path-static] * Reads from `extern` statics are not allowed in any constant evaluation context. * If the evaluation is *not* carried out in an initializer of a `static` item, then reads from any mutable `static` are not allowed. A mutable `static` is a `static mut` item, or a `static` item with an interior-mutable type. -These requirements are checked only when the constant is evaluated. In other words, having such accesses syntactically occur in const contexts is allowed as long as they never get executed. + These requirements are checked only when the constant is evaluated. In other words, having such accesses syntactically occur in const contexts is allowed as long as they never get executed. r[const-eval.const-expr.tuple] * [Tuple expressions].