-
Notifications
You must be signed in to change notification settings - Fork 410
Implement std::error::Error for SocketParseError #3816
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
base: main
Are you sure you want to change the base?
Implement std::error::Error for SocketParseError #3816
Conversation
SocketParseError does not implement std Error which means it can't be used in standard ways like combining ? and anyhow. This commit implements std::error::Error for SocketParseError
👋 I see @TheBlueMatt was un-assigned. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3816 +/- ##
==========================================
+ Coverage 89.73% 89.75% +0.01%
==========================================
Files 159 159
Lines 128910 128910
Branches 128910 128910
==========================================
+ Hits 115676 115698 +22
+ Misses 10536 10511 -25
- Partials 2698 2701 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Hide the std::error::Error for SocketAddressParseError implementation behind the "std" feature since it relies on the standard library.
🔔 1st Reminder Hey @TheBlueMatt! This PR has been waiting for your review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, why not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, please go ahead and squash the fixup so that all CI checks pass.
SocketParseError does not implement std Error which means it can't be used in standard ways like combining ? and anyhow. This is problematic since it's a public interface and being able to use anyhow on public errors is nice.
This commit implements std::error::Error for SocketParseError