Closed deepfire closed 6 years ago
What version of megaparsec do you use?
The conflicting instance is introduced in upstream commit https://github.com/mrkkrp/megaparsec/commit/dd2386aafc6b23553dda3ae0bc97cba80cf4124a#diff-7762a64005e439e93f28d5c9a983baa9
sure but there is a megaparsec <5.2 constraint in the cabal file
Sigh, yes, but.. I had to "jailbreak", using Nix terms, because I had to go with the latest nixpkgs
.. Of course, with the benefit of the hindsight I would have overridden megaparsec
to an earlier version -- but that wouldn't have been free either, since it would've meant rebuilding things from source..
It's not a simple picture, and I agree, personal inclinations did play a role in this.
But in any case, we now have an option to have compat with the latest megaparsec : -)
I see. I'm not a nix user. Usually I use stack
or cabal new-build
in local sandboxed mode.
Why did you close the issue? Did you solve it?
The latest lambdacube-compiler
builds with MegaParsec 6.3.0, with #13 -- so I've closed that issue.
Also, the changes from #13 solve different MegaParsec issues -- the RWST instance conflict apparently is no longer a problem.
This seems to work for my test application.
EDIT: there was a controversy, due to launching a different application and thinking that something is broken.