Cargo: Handle errors properly in cargo-marker
#169
Labels
A-marker-cargo
Area: All things connected to `cargo_marker`
C-enhancement
Category: New feature or request
E-good-first-issue
Participation: Good for newcomers
Milestone
cargo-marker
interacts a lot with other programs or the file system. Therefore, it has to handle numerousResult<X, Y>
types. Currently, every error is just mapped to a singleExitStatus
enum, that provides very little information. This is not ideal...cargo_marker
should "know" what an exit status is.The text was updated successfully, but these errors were encountered: