notohh/rustlings
notohh/rustlings
1
0
Fork 0
mirror of https://github.com/notohh/rustlings.git synced 2024-11-25 14:57:32 -05:00
Code Issues Projects Releases Packages Wiki Activity
rustlings/exercises/error_handling
History
Taylor Yu b7ddd09fab address review feedback 
Adjust error text and naming to conform with best practices.
Use `map_err()` instead of `or()`. Wrap lower-level errors instead of
ignoring their details.

Also, don't "cheat" by bypassing the `new()` function in tests.

Fix a dangling reference in the try_from_into hints.
2021-06-09 23:27:53 -05:00
..
errors1.rs Merge branch 'master' into refactor-hints 2019-11-11 17:21:06 +01:00
errors2.rs Merge branch 'master' into refactor-hints 2019-11-11 17:21:06 +01:00
errors3.rs Merge branch 'master' into refactor-hints 2019-11-11 17:21:06 +01:00
errors4.rs fix: rename result1 to errors4 2021-06-06 23:08:54 -05:00
errors5.rs address review feedback 2021-06-09 23:27:53 -05:00
errors6.rs address review feedback 2021-06-09 23:27:53 -05:00
README.md docs(exercises): updated all exercises readme files 2021-04-23 19:54:31 +02:00

README.md

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