From f344d569b4b7bfea91813ff3e8c1b405c6bf4945 Mon Sep 17 00:00:00 2001 From: Maybe Waffle Date: Sun, 29 May 2022 13:14:59 +0400 Subject: [PATCH] Fix typo (panick -> panic) --- library/std/src/error.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/library/std/src/error.rs b/library/std/src/error.rs index c2d30616019c7..87f213b160830 100644 --- a/library/std/src/error.rs +++ b/library/std/src/error.rs @@ -52,7 +52,7 @@ //! to convey your intent and assumptions which makes tracking down the source //! of a panic easier. `unwrap` on the other hand can still be a good fit in //! situations where you can trivially show that a piece of code will never -//! panick, such as `"127.0.0.1".parse::().unwrap()` or early +//! panic, such as `"127.0.0.1".parse::().unwrap()` or early //! prototyping. //! //! # Common Message Styles