From 613c03321a0970cce3a5d04ede04ab4a24ac1dbb Mon Sep 17 00:00:00 2001 From: Andrew Kelley Date: Wed, 12 Aug 2026 18:50:04 -0700 Subject: [PATCH] langref: fix typos introduced in ac8a8d0c5996bbf627438768e3c23154a6404183 --- doc/langref.html.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/langref.html.in b/doc/langref.html.in index 0084e01b2e30d0d22ddc233d2fe2aa899fc6b6ed..974acb49716d37308f88150d92c2a6ac3268127c 100644 --- a/doc/langref.html.in +++ b/doc/langref.html.in @@ -5015,12 +5015,12 @@ fn cmpxchgWeakButNotAtomic(comptime T: type, ptr: *T, expected_value: T, new_val in an API runs the risk of introducing dead code into the codebase, unnoticed. For example, if the field is ever renamed, code which uses {#syntax#}@hasDecl{#endsyntax#} will compile successfully while failing - to enable or disable an intended block of code. Even a simple a typo in + to enable or disable an intended block of code. Even a simple typo in the field name passed to {#syntax#}@hasDecl{#endsyntax#} would go unnoticed by the compiler. Thus, it is safer to use alternative methods to check for the presence or absence of a particular declaration where possible. For example, if the target operating system would indicate whether a particular - function is available, it more maintainable to check + function is available, it is more maintainable to check {#syntax#}@import("builtin").target.os.tag{#endsyntax#} rather than {#syntax#}@hasDecl{#endsyntax#}.

-- 2.54.0