|about 1 month ago||over 1 year ago|
|LicenseRef-PublicDomain||BSD 3-clause "New" or "Revised" License|
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.
3 projects | /r/haskell | 10 Sep 2021
Nice! Thanks for including a comparison with my package typelevel-rewrite-rules. Since my package indeed struggles with infinite loops introduced by self-triggering rewrite rules, I would like to better understand why your package doesn't suffer from that same problem.
Transpiling to GHC Core language
4 projects | /r/haskell | 30 Apr 2021
When writing a typechecker plugin, you can eliminate constraints from the user's program by providing an implementation of the corresponding dictionary. The way you provide that dictionary to ghc is by providing a core expression; for example, this evCast futureDict co expression has type EvTerm, whose first constructor takes an EvExpr, which is a synonym for CoreExpr.
[GHC Proposals] GHC Maintainer preview
4 projects | /r/haskell | 3 Apr 2021
Until then, I guess we can simply poll. Here's a GitHub Action I wrote today which checks if the latest report for a given package includes a failure: https://github.com/gelisam/typelevel-rewrite-rules/blob/main/.github/workflows/check-hackage-matrix.yml
We haven't tracked posts mentioning type-level-numbers yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
funspection - Type-level function utilities
type-eq - Type equality evidence you can carry around
uom-plugin - Units of measure as a GHC typechecker plugin
constraint-rules - Extend GHC's type checker with user-defined rules, without writing a type checker plugin.