ghc-proposals
Proposed compiler and language changes for GHC and GHC/Haskell (by KoenP)
bidirectional-instances
This package contains class for bidirectional instances and TH methods for generating instances for it. (by Lev135)
| ghc-proposals | bidirectional-instances | |
|---|---|---|
| 1 | 1 | |
| 0 | 2 | |
| - | - | |
| 10.0 | 10.0 | |
| over 4 years ago | almost 2 years ago | |
| Haskell | ||
| - | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ghc-proposals
Posts with mentions or reviews of ghc-proposals.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-02.
-
Bidirectional instance constraints -- pros&cons. Need your opinion
Link to the proposal
bidirectional-instances
Posts with mentions or reviews of bidirectional-instances.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-02.
-
Bidirectional instance constraints -- pros&cons. Need your opinion
Some weeks ago, I asked here, if there is a way to let GHC infer backwards constraints from instance declaration, i. e. for instance instance (A a) => B a where have not only forall a. A a => B a, but also forall a. B a => A a. It's correct, provided that we have no overlapping instance for B. In answers there were a link to an article on this topic. However, implementation from the article requires essential changes in GHC. I found some way to make this with currently available extensions (mostly type families) with not so much boilerplate and now uploaded it on github with my solution for the first problem from the "Motivation" section of the paper.
What are some alternatives?
When comparing ghc-proposals and bidirectional-instances you can also consider the following projects:
ghc-proposals - Proposed compiler and language changes for GHC and GHC/Haskell