From 88994ea5d2fae0ef50d6f8787ad85cc626b67ac2 Mon Sep 17 00:00:00 2001 From: Ralf Biedert Date: Wed, 2 Sep 2026 17:25:37 +0200 Subject: [PATCH 1/2] Update M-PANIC-CONTINUATION.md --- src/guidelines/correctness/M-PANIC-CONTINUATION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guidelines/correctness/M-PANIC-CONTINUATION.md b/src/guidelines/correctness/M-PANIC-CONTINUATION.md index 4bef419..2a447b0 100644 --- a/src/guidelines/correctness/M-PANIC-CONTINUATION.md +++ b/src/guidelines/correctness/M-PANIC-CONTINUATION.md @@ -30,4 +30,4 @@ fn main() { Although the example above is slightly contrived, the side effects and interactions of a caught panic can be harder to identify, can have wide blast radius, and be subtle. -Systems where many unrelated tasks are in flight (e.g., server request handlers) can use `catch_unwind` on a per-request basis, but should still promote an application restart after a request handler caused a panic. The purpose of `catch_unwind` here is not to continue execution indefinitely, but to allow all other requests to gracefully finish. +Systems where many unrelated tasks are in flight (e.g., server request handlers or runtime worker threads) should promote an application restart after an observed panic. From de976ceeb75439663d9c8d80eb6dc93f2d502d01 Mon Sep 17 00:00:00 2001 From: Ralf Biedert Date: Wed, 2 Sep 2026 17:26:58 +0200 Subject: [PATCH 2/2] Fix formatting issue in M-PANIC-CONTINUATION.md --- src/guidelines/correctness/M-PANIC-CONTINUATION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guidelines/correctness/M-PANIC-CONTINUATION.md b/src/guidelines/correctness/M-PANIC-CONTINUATION.md index 2a447b0..af10544 100644 --- a/src/guidelines/correctness/M-PANIC-CONTINUATION.md +++ b/src/guidelines/correctness/M-PANIC-CONTINUATION.md @@ -30,4 +30,4 @@ fn main() { Although the example above is slightly contrived, the side effects and interactions of a caught panic can be harder to identify, can have wide blast radius, and be subtle. -Systems where many unrelated tasks are in flight (e.g., server request handlers or runtime worker threads) should promote an application restart after an observed panic. +Systems where many unrelated tasks are in flight (e.g., server request handlers or runtime worker threads) should promote an application restart after an observed panic.