mirror of
https://github.com/mainmatter/100-exercises-to-learn-rust
synced 2024-12-26 21:58:49 +01:00
add system to sentence (#48)
This commit is contained in:
parent
7a4fa2d1f4
commit
6d707bb32d
1 changed files with 1 additions and 1 deletions
|
@ -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:
|
||||||
|
|
Loading…
Reference in a new issue