Skip to content

Make ParseError a std::error::Error #298

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.

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

Closed
wants to merge 1 commit into from

Conversation

lucacasonato
Copy link
Contributor

Previously the ParseError struct did not implement
std::error::Error or std::fmt::Display. This meant that ParseError
was not boxable into an "any error" box like anyhow::Error. This
commit adds Error and Display implementations for ParseError and
friends.

Previously the `ParseError` struct did not implement
`std::error::Error` or `std::fmt::Display`. This meant that `ParseError`
was not boxable into an "any error" box like `anyhow::Error`. This
commit adds Error and Display implementations for ParseError and
friends.
@emilio
Copy link
Member

emilio commented Apr 27, 2023

@bors-servo r+

@bors-servo
Copy link
Contributor

📌 Commit 1e72363 has been approved by emilio

@bors-servo
Copy link
Contributor

⌛ Testing commit 1e72363 with merge b395540...

bors-servo added a commit that referenced this pull request Apr 27, 2023
Make `ParseError` a `std::error::Error`

Previously the `ParseError` struct did not implement
`std::error::Error` or `std::fmt::Display`. This meant that `ParseError`
was not boxable into an "any error" box like `anyhow::Error`. This
commit adds Error and Display implementations for ParseError and
friends.
@bors-servo
Copy link
Contributor

💔 Test failed - checks-github

bors-servo added a commit that referenced this pull request Apr 27, 2023
Make `ParseError` a `std::error::Error`

Previously the `ParseError` struct did not implement `std::error::Error` or `std::fmt::Display`. This meant that `ParseError` was not boxable into an "any error" box like `anyhow::Error`. This commit adds Error and Display implementations for ParseError and friends.

Rebase + MSRV fix of #298
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants