From a2956d72e1bb66e7d22eaae84a02c1c1acd204f2 Mon Sep 17 00:00:00 2001 From: Darius Wiles Date: Fri, 22 Mar 2024 16:26:26 -0700 Subject: [PATCH] Fix typo in comments --- library/core/src/pin.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/library/core/src/pin.rs b/library/core/src/pin.rs index a0227d9130bb7..74477f6a563ec 100644 --- a/library/core/src/pin.rs +++ b/library/core/src/pin.rs @@ -187,7 +187,7 @@ //! Although there were other reason as well, this issue of expensive composition is the key thing //! that drove Rust towards adopting a different model. It is particularly a problem //! when one considers, for exapmle, the implications of composing together the [`Future`]s which -//! will eventaully make up an asynchronous task (including address-sensitive `async fn` state +//! will eventually make up an asynchronous task (including address-sensitive `async fn` state //! machines). It is plausible that there could be many layers of [`Future`]s composed together, //! including multiple layers of `async fn`s handling different parts of a task. It was deemed //! unacceptable to force indirection and allocation for each layer of composition in this case.