From 03279d2d390d48134e6a6797280d9cea7acda931 Mon Sep 17 00:00:00 2001 From: Tanish-Eagle Date: Tue, 9 Aug 2022 18:09:25 +0530 Subject: [PATCH] Fixed spellings and clarified some sentances --- en/src/result-panic/panic.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en/src/result-panic/panic.md b/en/src/result-panic/panic.md index b4ada83..da71ba6 100644 --- a/en/src/result-panic/panic.md +++ b/en/src/result-panic/panic.md @@ -73,7 +73,7 @@ thread 'main' panicked at 'index out of bounds: the len is 3 but the index is 99 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` -Though there is the panic reason and code line showing here, but sometime we want to get more info about the call stack. +Though there is the reason of panic and the line of the code is showing where the panic has occured, sometimes we want to get more info about the call stack. 3. 🌟 ```shell @@ -99,7 +99,7 @@ note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose bac ``` ### `unwinding` and `abort` -By default, when a `panic` occurs, the program starts *unwinding*, which means Rust walks back up the stack and cleans up the data from each function it encouters. +By default, when a `panic` occurs, the program starts *unwinding*, which means Rust walks back up the stack and cleans up the data from each function it encounters. But this walk back and clean up is a lot of work. The alternative is to immediately abort the program without cleaning up.