From b884e4d513e668b72f60f456b5e6bbcc3653ee88 Mon Sep 17 00:00:00 2001 From: l0ng-ai <24760907+l0ng-ai@users.noreply.github.com> Date: Sun, 23 Aug 2026 13:54:08 +0800 Subject: [PATCH] docs(rustdoc): repair the two links that broke the gate this branch added MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The rustdoc gate is one this branch put in CI, and this branch had left it failing — which is the worst state for a gate to be in, since it reads as enforced and enforces nothing. `displayed_registry` was the lower-case spelling of `DisplayedRegistry`, so it resolves now. `PIP_SIZE` names nothing anywhere in the tree; rather than guess which constant it used to be, the sentence now points at the rem-sized constants it was contrasting against, which is the part that was actually true. All six CI gates now pass as CI runs them: fmt, host boundary, clippy with `-D warnings`, rustdoc with `-D warnings`, the suite under `--locked`, and the updater's own feature build. --- src/terminal/view.rs | 2 +- src/ui/right_panel.rs | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/terminal/view.rs b/src/terminal/view.rs index 5f4cfd24..3d0e171d 100644 --- a/src/terminal/view.rs +++ b/src/terminal/view.rs @@ -216,7 +216,7 @@ pub struct TerminalView { /// "preparation failed" — see [`staging_cache`]. remote_clipboard_dir: Option, pub focus_handle: FocusHandle, - /// See [`displayed_registry`]. Shared with the registry so the app can + /// See [`DisplayedRegistry`]. Shared with the registry so the app can /// flip it during a draw without an entity access. displayed: std::sync::Arc, pub font: Font, diff --git a/src/ui/right_panel.rs b/src/ui/right_panel.rs index 2e74f03f..76298214 100644 --- a/src/ui/right_panel.rs +++ b/src/ui/right_panel.rs @@ -1443,8 +1443,8 @@ pub(crate) fn git_badge(letter: &str, color: gpui::Hsla, mono: &gpui::SharedStri /// /// The padding and radius are in pixels while the text is in rems, so the two /// stop being derived from each other once the interface font scale leaves -/// 100%: the text grows and the padding does not. That is the same trap -/// [`PIP_SIZE`] below is written in rems to avoid, and this chip has not been +/// 100%: the text grows and the padding does not. That is the same trap the +/// rem-sized constants above are written to avoid, and this chip has not been /// through it yet. pub(crate) fn info_chip( text: &str,