diff options
| author | Walter Kalata <ping@walter.dev> | 2024-06-07 12:18:43 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-06-07 12:18:43 -0700 |
| commit | f82f0530f36914545820f6307f73ab024fb82441 (patch) | |
| tree | fe480c169370316a658040a59e81f934e686a849 | |
| parent | e3c3ce62d7a8328120aa2abf60a34576f3862fde (diff) | |
| download | rust-f82f0530f36914545820f6307f73ab024fb82441.tar.gz rust-f82f0530f36914545820f6307f73ab024fb82441.zip | |
Fix typo in docs for std::pin
| -rw-r--r-- | library/core/src/pin.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/library/core/src/pin.rs b/library/core/src/pin.rs index d8fc3b7177f..0d2aa3070a1 100644 --- a/library/core/src/pin.rs +++ b/library/core/src/pin.rs @@ -184,7 +184,7 @@ //! requires at least a level of pointer indirection each time a new object is added to the mix //! (and, practically, a heap allocation). //! -//! Although there were other reason as well, this issue of expensive composition is the key thing +//! Although there were other reasons 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 example, the implications of composing together the [`Future`]s which //! will eventually make up an asynchronous task (including address-sensitive `async fn` state |