-
Notifications
You must be signed in to change notification settings - Fork 1
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
Free theorems modernization roadmap #4
Comments
What's wrong with the present repo? |
Well nothing per-se. |
Only if noone else does it :-). It seems that right now you are most motivated, so why not keep it here? |
@alexfmpe Would you mind setting up a ci pipeline to run the project with some appropriate versions of GHC? I would then be happy to merge the PRs if they pass the compilation step. |
@ichistmeinname done: #6 |
There's 30-40 incomplete patterns laying around. For some of them it's obvious what to do, but in general I've been mostly doing
throwError
or documenting witherror
, depending on what's already there. Hardly ideal but still better thanNon-exhaustive patterns in function foo
, which is what we currently get for (intentionally or not) unsupported operations.I wanted to port just #3 to @nomeata's version to get one last useful/releasable step before the big merge/jump, but it required also porting the work getting
haskell-src-exts
to build for newer ghc, so meh.I do wonder if it makes sense for
free-theorems
to keep living as a standalone thing that has its own mini haskell AST types in addition to the ones inhaskell-src-exts
(which is now in life support). Would it be more at home inghci
under:i
or so? Maybe it could be a google summer of code or haskell foundation project.After all, the compiler already has everything in scope, and squeezing every bit of reasoning based on types alone is textbook haskell. I'm not sure if the theorems could also be useful for automatically obtaining rewrite rules or if that always needs human curation.
cc @ichistmeinname @nomeata
The text was updated successfully, but these errors were encountered: