rustlings/exercises/error_handling
Anish eacf7db6f3
refactor: Update comment to use correct construct name 'Result' instead of 'Option'
Refactor the comment in the code to provide a more accurate description of the construct being used. Replace the mention of Option with Result.
2023-06-23 17:18:17 +05:45
..
errors1.rs refactor: Update comment to use correct construct name 'Result' instead of 'Option' 2023-06-23 17:18:17 +05:45
errors2.rs docs: cleanup the explanation paragraphs at the start of each exercise. 2023-05-29 18:41:51 +01:00
errors3.rs docs: cleanup the explanation paragraphs at the start of each exercise. 2023-05-29 18:41:51 +01:00
errors4.rs docs: cleanup the explanation paragraphs at the start of each exercise. 2023-05-29 18:41:51 +01: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