rust/comprehensive-rust
1
0
Fork 0
mirror of https://github.com/google/comprehensive-rust.git synced 2025-11-29 08:57:20 +02:00
Code Issues Releases Activity

docs: improve language in error-handling section (#2886)

Browse Source 
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!

As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
This commit is contained in:
Martin Geisler
2025-09-06 18:51:21 +02:00
committed by GitHub
parent 041fa6b9c2
commit afcc3a47c0
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/error-handling/panics.md
View File

@@ -4,9 +4,7 @@ minutes: 3
# Panics
Rust handles fatal errors with a "panic".
Rust will trigger a panic if a fatal error happens at runtime:
In case of a fatal runtime error, Rust triggers a "panic":
```rust,editable,should_panic
fn main() {
@@ -17,8 +15,8 @@ fn main() {
- Panics are for unrecoverable and unexpected errors.
- Panics are symptoms of bugs in the program.
- Runtime failures like failed bounds checks can panic
- Assertions (such as `assert!`) panic on failure
- Runtime failures like failed bounds checks can panic.
- Assertions (such as `assert!`) panic on failure.
- Purpose-specific panics can use the `panic!` macro.
- A panic will "unwind" the stack, dropping values just as if the functions had
returned.