Truth
Changes and Pinafore projects. Pull requests not accepted. (by AshleyYakeley)
witness
By AshleyYakeley
| Truth | witness | |
|---|---|---|
| 5 | 1 | |
| 31 | 4 | |
| - | - | |
| 9.3 | 5.2 | |
| 6 days ago | 9 months ago | |
| Haskell | Haskell | |
| GNU General Public License v3.0 only | BSD 2-clause "Simplified" 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.
Truth
Posts with mentions or reviews of Truth.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-01.
-
Implicit parameters vs ReaderT
Here's an example in Pinafore's type unifier code, where I use ?rigidity :: String -> NameRigidity everywhere. In my opinion, the implicit parameter constraint makes the already complicated code slightly simpler. But it doesn't escape the module.
-
[RFC] Generate Cabal files from TOML
I'm actually using YAML file includes with hpack to include a common.yaml file for settings common to multiple packages.
-
install package into haskell project
HPack is YAML, so it allows file inclusion. I use this to keep common settings for a multi-package project.
-
First Class Monad Stacks
I've got something pretty similar in an unreleased package.
-
Is this type family shenanigan safe?
I have now stripped out all that complication and replaced it with typeIsPair.
witness
Posts with mentions or reviews of witness.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-02.
-
Is this type family shenanigan safe?
This is what I originally did. I had a class called InKind that provided a witness to the fact that a given type of a given kind really was a "true" member of the kind. In the case of kind Type, that was all types, so a null witness was fine. In the case of kind (kp,kq) that was a witness to the particular two components of the type.
What are some alternatives?
When comparing Truth and witness you can also consider the following projects:
cleff - Fast and concise extensible effects
hpack - hpack: A modern format for Haskell packages