Skip to content

Error type convention #33

@mappum

Description

@mappum

We will probably eventually need a more advanced convention for error types - we currently just use the one-size-fits-all failure::Error, but this might be hard when we need to match on error types in the future. It might work to use failure::Fail enums everywhere and still use failure::Error then just attempt to downcast, but we should experiment first before applying a convention to the whole codebase.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions