Skip to content

Use thiserror for strongly typed errors instead of anyhow #2

Description

@fwcd

While anyhow is convenient for emitting human-readable errors, its errors are generally unsuitable for catching. We work around this by nesting Option with Result in receive_raw and receive_message, but this quickly becomes unergonomic and returning a custom error as we do in lighthouse-client might be a better idea.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions