urie
/
100-exercises-to-learn-rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix links.

This commit is contained in:
LukeMathWalker 2024-05-22 11:03:19 +02:00
parent 9bda4eb7e0
commit e5eee2e83c
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
book/src/04_traits/12_drop.md
View File

@ -1,6 +1,6 @@
# The `Drop` trait # The `Drop` trait
When we introduced [destructors](../../02_ticket_v1/11_destructor/README.md), When we introduced [destructors](../03_ticket_v1/11_destructor),
we mentioned that the `drop` function: we mentioned that the `drop` function:
1. reclaims the memory occupied by the type (i.e. `std::mem::size_of` bytes) 1. reclaims the memory occupied by the type (i.e. `std::mem::size_of` bytes)

2
book/src/05_ticket_v2/01_enum.md
View File

@ -1,6 +1,6 @@
# Enumerations # Enumerations
Based on the validation logic you wrote [in a previous chapter](../../02_ticket_v1/02_validation), Based on the validation logic you wrote [in a previous chapter](../03_ticket_v1/02_validation),
there are only a few valid statuses for a ticket: `To-Do`, `InProgress` and `Done`. there are only a few valid statuses for a ticket: `To-Do`, `InProgress` and `Done`.
This is not obvious if we look at the `status` field in the `Ticket` struct or at the type of the `status` This is not obvious if we look at the `status` field in the `Ticket` struct or at the type of the `status`
parameter in the `new` method: parameter in the `new` method: