Skip to content
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

Jump to bottom

aborting-on-panic.md: Typo in example config #125

Merged
merged 1 commit into from
Jan 10, 2019
Merged

aborting-on-panic.md: Typo in example config #125

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions src/rust-2018/error-handling-and-panics/aborting-on-panic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ By default, Rust programs will unwind the stack when a `panic!` happens. If you'
immediate abort instead, you can configure this in `Cargo.toml`:

```toml
[profile.debug]
[profile.dev]
panic = "abort"

[profile.release]
Expand All @@ -15,4 +15,4 @@ panic = "abort"

Why might you choose to do this? By removing support for unwinding, you'll
get smaller binaries. You will lose the ability to catch panics. Which choice
is right for you depends on exactly what you're doing.
is right for you depends on exactly what you're doing.