about summary refs log tree commit diff
diff options
context:
space:
mode:
authorvxpm <59714841+vxpm@users.noreply.github.com>2021-09-28 17:53:12 -0300
committerGitHub <noreply@github.com>2021-09-28 17:53:12 -0300
commit30ea0a5ebb2694dbb70c18dfb1fccfe95b191001 (patch)
tree41d05c3e42a5b5b6d3c25a79c8d046e71c838346
parentfb17671eb07fc9f68c17b7494e402591fe08b299 (diff)
downloadrust-30ea0a5ebb2694dbb70c18dfb1fccfe95b191001.tar.gz
rust-30ea0a5ebb2694dbb70c18dfb1fccfe95b191001.zip
Fix typo ("asynx" corrected to "async")
-rw-r--r--clippy_lints/src/await_holding_invalid.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/clippy_lints/src/await_holding_invalid.rs b/clippy_lints/src/await_holding_invalid.rs
index 0cc79c8b6e8..28615b9217c 100644
--- a/clippy_lints/src/await_holding_invalid.rs
+++ b/clippy_lints/src/await_holding_invalid.rs
@@ -16,7 +16,7 @@ declare_clippy_lint! {
     /// The Mutex types found in std::sync and parking_lot
     /// are not designed to operate in an async context across await points.
     ///
-    /// There are two potential solutions. One is to use an asynx-aware Mutex
+    /// There are two potential solutions. One is to use an async-aware Mutex
     /// type. Many asynchronous foundation crates provide such a Mutex type. The
     /// other solution is to ensure the mutex is unlocked before calling await,
     /// either by introducing a scope or an explicit call to Drop::drop.