Skip to content
This repository has been archived by the owner on Aug 25, 2023. It is now read-only.

Evaluate usage of anyhow crate #25

Closed
joshuabenuck opened this issue Aug 24, 2020 · 0 comments
Closed

Evaluate usage of anyhow crate #25

joshuabenuck opened this issue Aug 24, 2020 · 0 comments
Labels
enhancement New feature or request help welcome Help is welcome on this issue. rust

Comments

@joshuabenuck
Copy link
Contributor

Summary

PR #3 introduced the usage of the anyhow crate. anyhow is targeted at usage by applications and not libraries. See this post for a good overview on why this matters.

Desired Behavior

Our error handling crate should not appear in our public API since the favored error handling crate changes over time (as demonstrated by the failure crate being deprecated).

Possible Solution

We should consider switching to thiserror or a similar error handling crate targeted at libraries instead of applications.

@joshuabenuck joshuabenuck added the enhancement New feature or request label Aug 24, 2020
@Miriam-R Miriam-R added help welcome Help is welcome on this issue. on hold On hold until further notice labels Jan 20, 2021
@Miriam-R Miriam-R moved this from To Do to Backlog - Issues without a committed date. in PHP/C Engineering Board Jan 20, 2021
@Miriam-R Miriam-R removed the on hold On hold until further notice label Feb 10, 2021
@Ak-x Ak-x added the rust label Mar 8, 2022
@Ak-x Ak-x closed this as completed Aug 24, 2023
PHP/C Engineering Board automation moved this from Backlog - Issues without a committed date. to Done Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request help welcome Help is welcome on this issue. rust
Projects
Development

No branches or pull requests

3 participants