about summary refs log tree commit diff
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-11-02 12:14:15 +0100
committerGitHub <noreply@github.com>2024-11-02 12:14:15 +0100
commitc4024585a418a732d9ae13017373b4f8b84b3ab2 (patch)
tree42948eb7578316c7ee491b6f1cfc47326bce5e95
parentbfcd9ecea6cab6f4073931666e9ebbd557089306 (diff)
parent102fac7af6152653823586e1666d9322e6ca7eae (diff)
Rollup merge of #132495 - Houtamelo:remove_unintended_link, r=jieyouxu
Remove unintended link

Since `#[link_section]` is enclosed in braces, it was being confused with a link during docs compilation.

This caused compilation to fail when running `x dist` since it emitted a warning regarding broken links.
-rw-r--r--library/std/src/sys/thread_local/guard/windows.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/library/std/src/sys/thread_local/guard/windows.rs b/library/std/src/sys/thread_local/guard/windows.rs
index 7ee8e695c75..1752b0e1208 100644
--- a/library/std/src/sys/thread_local/guard/windows.rs
+++ b/library/std/src/sys/thread_local/guard/windows.rs
@@ -26,7 +26,7 @@
 //! This apparently translates to any callbacks in the ".CRT$XLB" section
 //! being run on certain events.
 //!
-//! So after all that, we use the compiler's #[link_section] feature to place
+//! So after all that, we use the compiler's `#[link_section]` feature to place
 //! a callback pointer into the magic section so it ends up being called.
 //!
 //! # What's up with this callback?