Skip to content

Consider replacing ParseIntError usage with a new Error struct #16

@kaidokert

Description

@kaidokert

Using ParseIntError is clunky as it can't be directly constructed, hence hacks like make_parse_int_err to make_neg_overflow_err. It could be cleaner to just have a proper Error struct for this.

Same applies for usage of core::fmt::Error

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions