From db317aeb90ec7dcc67909e2063b4955f48ea9a38 Mon Sep 17 00:00:00 2001 From: Marijn Schouten Date: Wed, 1 Jul 2026 19:50:45 +0200 Subject: [PATCH] Clarify text about futures in a vector --- src/ch17-05-traits-for-async.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/ch17-05-traits-for-async.md b/src/ch17-05-traits-for-async.md index 4b502ceafe..4e4441c4a1 100644 --- a/src/ch17-05-traits-for-async.md +++ b/src/ch17-05-traits-for-async.md @@ -130,10 +130,11 @@ yet ready. ### The `Pin` Type and the `Unpin` Trait Back in Listing 17-13, we used the `trpl::join!` macro to await three -futures. However, it’s common to have a collection such as a vector containing -some number futures that won’t be known until runtime. Let’s change Listing -17-13 to the code in Listing 17-23 that puts the three futures into a vector -and calls the `trpl::join_all` function instead, which won’t compile yet. +futures. However, it’s common to have a collection, such as a vector, +containing many futures the exact number of which won’t be known until runtime. +Let’s change Listing 17-13 to the code in Listing 17-23 that puts the three +futures into a vector and calls the `trpl::join_all` function instead, +which won’t compile yet.