From 800e923824443df26e7cbf2ab106e376581abc99 Mon Sep 17 00:00:00 2001 From: Carl Fredrik Samson Date: Fri, 15 Jan 2021 16:18:56 +0100 Subject: [PATCH] reworded paragraph re #36 --- src/1_futures_in_rust.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/src/1_futures_in_rust.md b/src/1_futures_in_rust.md index 0de9e08..4145ac1 100644 --- a/src/1_futures_in_rust.md +++ b/src/1_futures_in_rust.md @@ -77,11 +77,8 @@ The key to these tasks is that they're able to yield control to the runtime's scheduler and then resume execution again where it left off at a later point. In contrast to leaf futures, these kind of futures do not themselves represent -an I/O resource. When we poll these futures they will run until they get to a -leaf function that blocks, where it yields control to the scheduler and waits -for some resource to signal us that it's ready so we can resume where we left -off. These futures can nest many non-leaf futures and will keep on going until -they get to a leaf-future which returns `Pending` when polled. +an I/O resource. When we poll them they will run until they get to a +leaf-future which returns `Pending` and then yield control to the scheduler. ## Runtimes