rustlings/exercises/error_handling
Matt Nield 642aac6f43
chore(errors2): minor description wording change
This commit makes a minor change in the wording of the description of the errors2 exercise to avoid potential confusion, changing:

"A player of the game will type in how many items they want to buy, and the `total_cost` function will calculate the total cost of the tokens."
to
"A player of the game will type in how many items they want to buy, and the `total_cost` function will calculate the total cost of the items."
2023-10-13 15:47:38 -04:00
..
errors1.rs fix(errors1): change Result to Option in exersise description 2023-08-25 21:49:22 +02:00
errors2.rs chore(errors2): minor description wording change 2023-10-13 15:47:38 -04:00
errors3.rs docs: cleanup the explanation paragraphs at the start of each exercise. 2023-05-29 18:41:51 +01:00
errors4.rs chore(errors4): improved comment 2023-07-28 23:05:01 +02:00
errors5.rs docs: cleanup the explanation paragraphs at the start of each exercise. 2023-05-29 18:41:51 +01:00
errors6.rs docs: cleanup the explanation paragraphs at the start of each exercise. 2023-05-29 18:41:51 +01:00
README.md docs(error_handling): resolve markdown linter warnings 2023-03-29 21:13:27 +03:30

Error handling

Most errors aren’t serious enough to require the program to stop entirely. Sometimes, when a function fails, it’s for a reason that you can easily interpret and respond to. For example, if you try to open a file and that operation fails because the file doesn’t exist, you might want to create the file instead of terminating the process.

Further information