Skip to content

Add Failure-based type class instances to document why some instances can not exist #72

@JordanMartinez

Description

@JordanMartinez

Per #71, an attempt was made to add Bifunctor to Map. While the implementation could be written that would type-check, the issue is that implementation wouldn't maintain the Ord invariant.

To document this issue, we should add instances for such type classes where the instance depends on a Fail constraint. Then if one uses the instance, they'll get notified of the underlying issue along with the proper way to do X.

We should list all the instances (if any) that should be added in this way for each type below:

  • Map
  • Set
  • NonEmptySet

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