From 6564403641afde8bf445914ec2996fe7219289ab Mon Sep 17 00:00:00 2001 From: Niko Matsakis Date: Thu, 19 Dec 2024 14:32:25 +0000 Subject: [PATCH] pacify merciless fmt --- compiler/rustc_mir_build/src/builder/scope.rs | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/compiler/rustc_mir_build/src/builder/scope.rs b/compiler/rustc_mir_build/src/builder/scope.rs index c5463e514c3..a51fe4c52fa 100644 --- a/compiler/rustc_mir_build/src/builder/scope.rs +++ b/compiler/rustc_mir_build/src/builder/scope.rs @@ -1396,9 +1396,9 @@ impl<'a, 'tcx> Builder<'a, 'tcx> { } /// Builds drops for `pop_scope` and `leave_top_scope`. -/// +/// /// # Parameters -/// +/// /// * `unwind_drops`, the drop tree data structure storing what needs to be cleaned up if unwind occurs /// * `scope`, describes the drops that will occur on exiting the scope in regular execution /// * `block`, the block to branch to once drops are complete (assuming no unwind occurs) @@ -1436,14 +1436,14 @@ fn build_scope_drops<'tcx>( // statement. For other functions we don't worry about StorageDead. The // drops for the unwind path should have already been generated by // `diverge_cleanup_gen`. - + // `unwind_to` indicates what needs to be dropped should unwinding occur. // This is a subset of what needs to be dropped when exiting the scope. // As we unwind the scope, we will also move `unwind_to` backwards to match, // so that we can use it should a destructor panic. let mut unwind_to = unwind_to; - // The block that we should jump to after drops complete. We start by building the final drop (`drops[n]` + // The block that we should jump to after drops complete. We start by building the final drop (`drops[n]` // in the diagram above) and then build the drops (e.g., `drop[1]`, `drop[0]`) that come before it. // block begins as the successor of `drops[n]` and then becomes `drops[n]` so that `drops[n-1]` // will branch to `drops[n]`. @@ -1492,7 +1492,7 @@ fn build_scope_drops<'tcx>( continue; } - // As in the `DropKind::Storage` case below: + // As in the `DropKind::Storage` case below: // normally lint-related drops are not emitted for unwind, // so we can just leave `unwind_to` unmodified, but in some // cases we emit things ALSO on the unwind path, so we need to adjust