about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2022-05-29 19:42:39 +0000
committerbors <bors@rust-lang.org>2022-05-29 19:42:39 +0000
commit28b891916d4c85cd10fb2e9cfa8bc836a2c459f3 (patch)
treef420eea5ea46e7ce7e1b3cc3635cd02058684e8c
parentbef2b7cd1c7bcb3393f10d5752fcf9ee3026bce8 (diff)
parentf344d569b4b7bfea91813ff3e8c1b405c6bf4945 (diff)
downloadrust-28b891916d4c85cd10fb2e9cfa8bc836a2c459f3.tar.gz
rust-28b891916d4c85cd10fb2e9cfa8bc836a2c459f3.zip
Auto merge of #97514 - WaffleLapkin:panick, r=Dylan-DPC
Fix typo (panick -> panic)

Fix typo (panick -> panic) in `std::error` module docs.
-rw-r--r--library/std/src/error.rs2
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