-
Notifications
You must be signed in to change notification settings - Fork 968
core::num::ParseIntError does not carry input #1113
Copy link
Copy link
Closed
Labels
1.0Issues and PRs required or helping to stabilize the APIIssues and PRs required or helping to stabilize the APIAPI breakThis PR requires a version bump for the next releaseThis PR requires a version bump for the next releaseerror handlingIssues and PRs related to error handling, mainly error refactoring epicIssues and PRs related to error handling, mainly error refactoring epic
Metadata
Metadata
Assignees
Labels
1.0Issues and PRs required or helping to stabilize the APIIssues and PRs required or helping to stabilize the APIAPI breakThis PR requires a version bump for the next releaseThis PR requires a version bump for the next releaseerror handlingIssues and PRs related to error handling, mainly error refactoring epicIssues and PRs related to error handling, mainly error refactoring epic
We can provide better error reporting if errors contain the value that caused them to be triggered. Currently we use
core::num::ParseIntError, perhaps we could have a new error typeParseIntError(String).