Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

errors: figure out if/how to expose ErrorKind #61

Open
cyphar opened this issue Sep 11, 2024 · 0 comments
Open

errors: figure out if/how to expose ErrorKind #61

cyphar opened this issue Sep 11, 2024 · 0 comments
Labels
api/rust Related to the Rust API.
Milestone
0.2.0

Comments

@cyphar
Copy link
Member

cyphar commented Sep 11, 2024

ErrorKind is quite useful for our tests and most library users would probably want it for some uses, but it probably needs to have a better-designed way of distinguishing errors (ErrorKind::InvalidArgument vs ErrorKind::OsError(Some(libc::EINVAL)) is kind of unfortunate, for instance).

Kind of related to #60.
@cyphar cyphar added the api/rust Related to the Rust API. label Sep 11, 2024
@cyphar cyphar added this to the 0.2.0 milestone Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api/rust Related to the Rust API.
Projects
None yet
Milestone
0.2.0
Development

No branches or pull requests
1 participant
@cyphar