michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-20 16:07:49 +00:00
Code Issues Projects Releases Wiki Activity

Fix links to Rust unstable book

Browse Source
This commit is contained in:
Philipp Oppermann
2024-02-08 19:06:38 +01:00
parent 71e5ea0268
commit 71f5d220ee
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
blog/content/edition-2/posts/12-async-await/index.md
View File

@@ -462,9 +462,9 @@ ExampleStateMachine::End(_) => {
Futures should not be polled again after they returned `Poll::Ready`, so we panic if `poll` is called while we are already in the `End` state.
We now know what the compiler-generated state machine and its implementation of the `Future` trait _could_ look like. In practice, the compiler generates code in a different way. (In case you're interested, the implementation is currently based on [_generators_], but this is only an implementation detail.)
We now know what the compiler-generated state machine and its implementation of the `Future` trait _could_ look like. In practice, the compiler generates code in a different way. (In case you're interested, the implementation is currently based on [_coroutines_], but this is only an implementation detail.)
[_generators_]: https://doc.rust-lang.org/stable/unstable-book/language-features/generators.html
[_coroutines_]: https://doc.rust-lang.org/stable/unstable-book/language-features/coroutines.html
The last piece of the puzzle is the generated code for the `example` function itself. Remember, the function header was defined like this: