Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
JordanMartinez opened this issue Jan 2, 2024 · 0 comments

Comments

@JordanMartinez
Copy link
Contributor

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant