Skip to content

Update M-PANIC-CONTINUATION.md #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Ralf Biedert (ralfbiedert) wants to merge 2 commits into
base: main
Choose a base branch
from
+1 −1
Open

Update M-PANIC-CONTINUATION.md #64

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
88994ea
Update M-PANIC-CONTINUATION.md
ralfbiedert Sep 2, 2026
de976ce
Fix formatting issue in M-PANIC-CONTINUATION.md
ralfbiedert Sep 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/guidelines/correctness/M-PANIC-CONTINUATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Loading