refactor: error handling #31

Open
opened 2025-10-14 01:15:23 +00:00 by treadful · 1 comment
Owner

Spend some time on error handling in general. Reduce the visual complexity. Move certain operations to utility functions so their errors can be reworked into the jot native.

Seeing this is better than a file full of match statements for different types of errors:

fn native() -> Result<(), Error> {
    let _ = do_thing()?;
    let _ = do_other()?;
}
Spend some time on error handling in general. Reduce the visual complexity. Move certain operations to utility functions so their errors can be reworked into the jot native. Seeing this is better than a file full of match statements for different types of errors: ```rust fn native() -> Result<(), Error> { let _ = do_thing()?; let _ = do_other()?; } ```
Author
Owner
https://salvo.rs/guide/topics/handle-error.html
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
treadful/jot#31
No description provided.