Open henrylaxen opened 4 years ago
I'm in a similar situation (but I'm not planning to give up on Fay for now, rather getting stuck on a version of GHC ;-). However, the other day I tried to compile with GHC-8.8.1 and manage to make it work after a few change. If you are interested you can find the code there (without guarantee).
I gave up in the end because I was trying to migrate my all project to GHC-8.8.1 and Fay wasn't the only problem.
Hi @henrylaxen, @maxigit,
I've heard about situation with haskell-src-exts
.
For sure, migration from haskell-src-exts
to ghc-lib
will be hard.
But I hope to retrieve 100-120h
this year to implement it.
If this activity succeed, then I will contact you with updates.
I hugely rely on fay
in my projects.
And also tried to migrate to 8.8.x
and ran into problems.
For me next step should to be implement GHC 8.8.x
support.
My apologise for the lack of responses.
In order to achieve 8.8.x
support for now, following dependencies should be resolved:
Fay 0.24.0.5
uploaded on hackage (with GHC 8.8 support): https://hackage.haskell.org/package/fay-0.24.0.5
@henrylaxen @maxigit thank you for your effort!
Meantime, in order to improve situation around Fay and resolve current issue, migration from haskell-src-exts
to ghc-lib
required as I described earlier.
Brilliant! Thank you
Fay 0.24.1.0
uploaded on hackage (GHC 8.10.1 support):
https://hackage.haskell.org/package/fay-0.24.1.0
Hi Guys,
I've been using fay for quite a few years now and in fact have contributed a few (usually minor) patches. I have been very happy with it, especially the simple fay <=> javascript ffi interface. I'm a little worried about the future of fay. Recently I tried to compile fay with the latest ghc (8.8.1) and ran into some problems. For example you guys are using an older version of haskell-src-exts, which is no longer being maintained. It is being replaced with ghc-lib. There was some other cruft that has been accumulating, but I don't remember what it was right now. I am considering switching the front end over to elm, but it would require a big investement in learning and rewriting existing code. So my question to you is: Is fay going to keep up with ghc development, or is it basically in a frozen state. Thanks for creating this cool piece of software, and I look forward to your response.
Best wishes, Henry Laxen