| @@ -184,7 +184,7 @@ |
|
|
| 184 |
184 |
//! requires at least a level of pointer indirection each time a new object is added to the mix |
| 185 |
185 |
//! (and, practically, a heap allocation). |
| 186 |
186 |
//! |
| 187 |
|
-//! Although there were other reason as well, this issue of expensive composition is the key thing |
|
187 |
+//! Although there were other reasons as well, this issue of expensive composition is the key thing |
| 188 |
188 |
//! that drove Rust towards adopting a different model. It is particularly a problem |
| 189 |
189 |
//! when one considers, for example, the implications of composing together the [`Future`]s which |
| 190 |
190 |
//! will eventually make up an asynchronous task (including address-sensitive `async fn` state |