From 561924db750cbb4e4c183f9616472ed9a5b0fc7f Mon Sep 17 00:00:00 2001 From: nsfisis Date: Wed, 12 Aug 2026 00:19:10 +0900 Subject: docs(todo): retag TODO markers by root cause Co-Authored-By: Claude Opus 5 (1M context) --- crates/shirabe/src/installer/installation_manager.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'crates/shirabe/src/installer/installation_manager.rs') diff --git a/crates/shirabe/src/installer/installation_manager.rs b/crates/shirabe/src/installer/installation_manager.rs index 8c26bdbc..2d21fb54 100644 --- a/crates/shirabe/src/installer/installation_manager.rs +++ b/crates/shirabe/src/installer/installation_manager.rs @@ -839,7 +839,7 @@ impl InstallationManager { return; } - // TODO(phase-c): PHP collects every http_downloader.add() promise and runs them via + // TODO(async): PHP collects every http_downloader.add() promise and runs them via // Loop::wait; the single-threaded sync bridge block_on's each notification serially instead. let result: anyhow::Result<()> = (|| -> anyhow::Result<()> { for (repo_url, packages) in self.notifiable_packages.borrow().iter() { @@ -966,7 +966,7 @@ impl InstallationManager { /// PHP: waitOnPromises() creates a ProgressBar up front and Loop::wait advances it while the /// concurrent promises resolve. - /// TODO(phase-c): Loop::wait has no active-job counter to feed the bar yet, so a + /// TODO(async): Loop::wait has no active-job counter to feed the bar yet, so a /// single 0% -> 100% jump is rendered after the wait instead of PHP's timing-driven /// intermediate snapshots. async fn wait_on_promises<'p>( -- cgit v1.3.1-4-g156e