-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add Alt ParseT instance #12
Comments
Sadly we can't give |
Sorry, I mean we can't give |
Ok, I see. As a side note, some parsers use the failing parser as identity for |
That wouldn't be an identity unfortunately, since we need Also there's no way of failing with an "empty" message right now - any failure must come with a specific reason. I think this is a good thing, as "empty" is always going to be a useless error message. The laws are documented at https://hackage.haskell.org/package/base-4.9.1.0/docs/Control-Applicative.html |
I just went through the exact same process as @alexbiehl and I would like to suggest the |
|
I use
cabal
to buildpurescript
and I found that your newest version 0.9.1.0 exports a custom(<|>)
which clashes withProtolude.<|>
which is a reexport fromControl.Applicative
. I noticed becauseLanguage.PureScript.Docs.Types
failed like crazy. Of course an upper bound onaeson-better-errors
helped but I think using the standardAlternative
instance prevents such incompatibilities in the first place.The text was updated successfully, but these errors were encountered: