diff options
| author | Maybe Waffle <waffle.lapkin@gmail.com> | 2022-05-29 13:14:59 +0400 |
|---|---|---|
| committer | Maybe Waffle <waffle.lapkin@gmail.com> | 2022-05-29 13:14:59 +0400 |
| commit | f344d569b4b7bfea91813ff3e8c1b405c6bf4945 (patch) | |
| tree | 4afa2de52b5a2a6db01c3c7ca760408f81ebe206 | |
| parent | 303d916867040e269b54adf3cfc7f5c903dc26ff (diff) | |
| download | rust-f344d569b4b7bfea91813ff3e8c1b405c6bf4945.tar.gz rust-f344d569b4b7bfea91813ff3e8c1b405c6bf4945.zip | |
Fix typo (panick -> panic)
| -rw-r--r-- | library/std/src/error.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/library/std/src/error.rs b/library/std/src/error.rs index c2d30616019..87f213b1608 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::<std::net::IpAddr>().unwrap()` or early +//! panic, such as `"127.0.0.1".parse::<std::net::IpAddr>().unwrap()` or early //! prototyping. //! //! # Common Message Styles |