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

Support for template-haskell 2.19? #40

Open
Demonstrandum opened this issue Nov 8, 2022 · 1 comment · May be fixed by #44
Open

Support for template-haskell 2.19? #40

Demonstrandum opened this issue Nov 8, 2022 · 1 comment · May be fixed by #44

Comments

@Demonstrandum
Copy link

The latest GHC versions use template-haskell-2.19.0.0, but this package is incompatible.

Unfortunately all GHC versions before 9.4.2 cause segfaults on my machine, otherwise I would just downgrade.

@nmeum
Copy link

nmeum commented Feb 21, 2023

FYI: freer-simple works fine for me with GHC 9.4.4 if I build my cabal project with --allow-newer so I guess this just requires widening the template-haskell dependency accordingly?

nmeum added a commit to nmeum/freer-simple that referenced this issue Mar 10, 2023
This allows freer-simple to be used with GHC 9.4.X. Prior versions
of template-haskell are not compatible with GHC 9.4. The 2.19 release
of template-haskell seems to be fully compatible with freer-simple.
That is, tests still pass and I haven't noticed any issues in my
own project (which use freer-simple).

Fixes lexi-lambda#40
nmeum added a commit to nmeum/freer-simple that referenced this issue May 16, 2024
This allows freer-simple to be used with GHC >= 9.4. Prior versions of
template-haskell are not compatible with those GHC versions. Newer
version of of template-haskell seem to be fully compatible with
freer-simple. That is, tests still pass and I haven't noticed any
issues in my own project (which use freer-simple).

Fixes lexi-lambda#40
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

Successfully merging a pull request may close this issue.

2 participants