From ee276abbd3a47eba7ff7f36972b0536502503f29 Mon Sep 17 00:00:00 2001 From: booleancoercion <33005025+booleancoercion@users.noreply.github.com> Date: Wed, 23 Dec 2020 10:44:59 +0200 Subject: [PATCH 1/3] Fixed a typo --- src/2_a_mental_model_for_futures.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/2_a_mental_model_for_futures.md b/src/2_a_mental_model_for_futures.md index 2da0907..8f38391 100644 --- a/src/2_a_mental_model_for_futures.md +++ b/src/2_a_mental_model_for_futures.md @@ -1,7 +1,7 @@ # A mental model of how Futures and runtimes work The main goal in this part is to build a high level -mental model of how the different pieces we read about in the previos chapter +mental model of how the different pieces we read about in the previous chapter works toghether. I hope this will make it easier to understand what we just read about in the previous chapter and also explain why we take a deep dive into topics like trait objects and generators in the next few chapters. @@ -72,4 +72,4 @@ this chapter._ slide19 - \ No newline at end of file + From d31b7976d18e89e6c7518a371f96c845953d7b06 Mon Sep 17 00:00:00 2001 From: booleancoercion <33005025+booleancoercion@users.noreply.github.com> Date: Wed, 23 Dec 2020 10:49:27 +0200 Subject: [PATCH 2/3] Caught another typo For some reason my mind skipped this one the first time I went over it... --- src/2_a_mental_model_for_futures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/2_a_mental_model_for_futures.md b/src/2_a_mental_model_for_futures.md index 8f38391..fbc1834 100644 --- a/src/2_a_mental_model_for_futures.md +++ b/src/2_a_mental_model_for_futures.md @@ -6,7 +6,7 @@ works toghether. I hope this will make it easier to understand what we just read about in the previous chapter and also explain why we take a deep dive into topics like trait objects and generators in the next few chapters. -This is not the only way to model this since we're making assumtions on runtime +This is not the only way to model this since we're making assumptions on runtime specifics that can vary a great deal, but it's the way I found it easiest to build upon. Finally, please note that the code itself is "pseudo-rust" due to the need for brevity and clarity. From d551e74443cf8f372a42bf59a5170c557f5c0afb Mon Sep 17 00:00:00 2001 From: booleancoercion <33005025+booleancoercion@users.noreply.github.com> Date: Wed, 23 Dec 2020 11:10:52 +0200 Subject: [PATCH 3/3] Fixed a typo (this time I think I didn't miss any) --- src/3_waker_context.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/3_waker_context.md b/src/3_waker_context.md index e5d4107..717d323 100644 --- a/src/3_waker_context.md +++ b/src/3_waker_context.md @@ -3,7 +3,7 @@ > **Overview:** > > - Understand how the Waker object is constructed -> - Learn how the runtime know when a leaf-future can resume +> - Learn how the runtime knows when a leaf-future can resume > - Learn the basics of dynamic dispatch and trait objects > > The `Waker` type is described as part of [RFC#2592][rfc2592].