darkicewolf50/RustBrock
1
0
Fork 0
mirror of https://github.com/darkicewolf50/RustBrock.git synced 2025-07-06 02:57:13 -06:00
Code Issues Actions Packages Projects Releases Wiki Activity

finished ch19 intro

Browse Source
This commit is contained in:
darkicewolf50
2025-04-08 11:54:40 -06:00
parent 849d24a10b
commit c3ea7d26e3
5 changed files with 56 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Implementing OO Design Pattern.md
View File

@ -346,7 +346,7 @@ Then we call the `unwrap` method, we know this will never panic.
We know the methods on `Post` ensure that `state` will always contain a `Some` value when those methods are done.
This is a case where we have more information than the compiler (previously discussed in [Ch 9]()) when we know that a `None` value is never possible, even though the compiler isn't able to understand that.
This is a case where we have more information than the compiler (previously discussed in [Ch 9](./Error%20Handling.md#cases-in-which-you-have-more-info-than-the-compiler)) when we know that a `None` value is never possible, even though the compiler isn't able to understand that.
Now at this point, when we call `content` on the `&Box<dyn State>`, deref coercion will take effect on the `&` and the `Box` so the `content` method will ultimately be called on the type that implements the `State` trait.