diff options
| author | Houtamelo <88971943+Houtamelo@users.noreply.github.com> | 2024-11-02 04:09:17 -0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-02 04:09:17 -0300 |
| commit | 102fac7af6152653823586e1666d9322e6ca7eae (patch) | |
| tree | c958bbd4c75e3ce29d2d051d8d00ca9fb2c804de | |
| parent | ef972a346668ed4234d1a43ed4ad7ca4e9c58d51 (diff) | |
| download | rust-102fac7af6152653823586e1666d9322e6ca7eae.tar.gz rust-102fac7af6152653823586e1666d9322e6ca7eae.zip | |
Remove unintended link
Since `#[link_section]` is enclosed in braces, it was being confused with a link during docs compilation.
| -rw-r--r-- | library/std/src/sys/thread_local/guard/windows.rs | 2 |
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? |