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

add system to sentence (#48)

This commit is contained in:
Onè 2024-05-24 06:58:07 -04:00 committed by GitHub
parent 7a4fa2d1f4
commit 6d707bb32d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
book/src/06_ticket_management/00_intro.md
View File

@ -2,7 +2,7 @@
In the previous chapter we modelled `Ticket` in a vacuum: we defined its fields and their constraints, we learned In the previous chapter we modelled `Ticket` in a vacuum: we defined its fields and their constraints, we learned
how to best represent them in Rust, but we didn't consider how `Ticket` fits into a larger system. how to best represent them in Rust, but we didn't consider how `Ticket` fits into a larger system.
We'll use this chapter to build a simple workflow around `Ticket`, introducing a (rudimentary) management to We'll use this chapter to build a simple workflow around `Ticket`, introducing a (rudimentary) management system to
store and retrieve tickets. store and retrieve tickets.
The task will give us an opportunity to explore new Rust concepts, such as: The task will give us an opportunity to explore new Rust concepts, such as: