Skip to content

feat: any errors that are used in publicly available traits need some method for creating that error. #3357

@ramfox

Description

@ramfox

Eg, in iroh-base, we have a trait Ticket, the method Ticket::from_bytes can return an iroh-base::ticket::ParseError, but there is no clean way to create a ParseError, since you would need to import other crates to fulfill the backtrace and span_tree fields inside the ParseError variant.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status

    👍 Ready

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions