From b5cddfa3f1c7e2f8c6bf28059b77b5d9e345138e Mon Sep 17 00:00:00 2001 From: Jonas Platte Date: Mon, 6 May 2019 15:35:07 +0200 Subject: [PATCH] Fix typo in controlling-panics-with-std-panic.md --- .../controlling-panics-with-std-panic.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/rust-2018/error-handling-and-panics/controlling-panics-with-std-panic.md b/src/rust-2018/error-handling-and-panics/controlling-panics-with-std-panic.md index 6c1bf634..3f4ae236 100644 --- a/src/rust-2018/error-handling-and-panics/controlling-panics-with-std-panic.md +++ b/src/rust-2018/error-handling-and-panics/controlling-panics-with-std-panic.md @@ -49,7 +49,7 @@ and so catching panics may not work. If your code relies on `catch_unwind`, you should add this to your Cargo.toml: ```toml -[profile.debug] +[profile.dev] panic = "unwind" [profile.release] @@ -77,4 +77,4 @@ paired with `resume_unwind`, which can then be used to restart the panicking process on the client of the pool, where it belongs. In both cases, you're introducing a new isolation boundary within a thread, and -then translating the panic into some other form of error elsewhere. \ No newline at end of file +then translating the panic into some other form of error elsewhere.