public-collect/books-futures-explained
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Small spelling corrections.

Browse Source
This commit is contained in:
James Robb
2020-05-19 10:37:38 +00:00
parent 6b41d2ff6d
commit 30b6e394c6
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/2_waker_context.md
View File

@@ -26,7 +26,7 @@ extend the ecosystem with new leaf-level tasks.
## The Context type ## The Context type
As the docs state as of now this type only wrapps a `Waker`, but it gives some As the docs state as of now this type only wraps a `Waker`, but it gives some
flexibility for future evolutions of the API in Rust. The context can for example hold flexibility for future evolutions of the API in Rust. The context can for example hold
task-local storage and provide space for debugging hooks in later iterations. task-local storage and provide space for debugging hooks in later iterations.
@@ -35,7 +35,7 @@ task-local storage and provide space for debugging hooks in later iterations.
One of the most confusing things we encounter when implementing our own `Future`s One of the most confusing things we encounter when implementing our own `Future`s
is how we implement a `Waker` . Creating a `Waker` involves creating a `vtable` is how we implement a `Waker` . Creating a `Waker` involves creating a `vtable`
which allows us to use dynamic dispatch to call methods on a _type erased_ trait which allows us to use dynamic dispatch to call methods on a _type erased_ trait
object we construct our selves. object we construct ourselves.
>If you want to know more about dynamic dispatch in Rust I can recommend an >If you want to know more about dynamic dispatch in Rust I can recommend an
article written by Adam Schwalm called [Exploring Dynamic Dispatch in Rust](https://alschwalm.com/blog/static/2017/03/07/exploring-dynamic-dispatch-in-rust/). article written by Adam Schwalm called [Exploring Dynamic Dispatch in Rust](https://alschwalm.com/blog/static/2017/03/07/exploring-dynamic-dispatch-in-rust/).
@@ -105,7 +105,7 @@ trait Test {
fn mul(&self) -> i32; fn mul(&self) -> i32;
} }
// This will represent our home brewn fat pointer to a trait object // This will represent our home-brewed fat pointer to a trait object
#[repr(C)] #[repr(C)]
struct FatPointer<'a> { struct FatPointer<'a> {
/// A reference is a pointer to an instantiated `Data` instance /// A reference is a pointer to an instantiated `Data` instance