You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When both branches of a ||| combinator produce a Failure as a result, the resulting error message is the one coming from the branch that matched the longest chain. This can lead to confusing error messages in situations like this one:
where the parser outputs an error message like expected 'int'. I think that it would be much less confusing to issue an error message that contains all the possible tokens: expected 'int' or 'double'.
Am I using the API the wrong way, or is there no way of configuring the parser to output such error messages? In the latter case, the addition of such a feature would be much appreciated.
The text was updated successfully, but these errors were encountered:
I think you might need to dig into the source code to answer this (and perhaps improve it) yourself, as I don't think there's anyone left who actually knows the codebase well.
When both branches of a
|||
combinator produce aFailure
as a result, the resulting error message is the one coming from the branch that matched the longest chain. This can lead to confusing error messages in situations like this one:where the parser outputs an error message like
expected 'int'
. I think that it would be much less confusing to issue an error message that contains all the possible tokens:expected 'int' or 'double'
.Am I using the API the wrong way, or is there no way of configuring the parser to output such error messages? In the latter case, the addition of such a feature would be much appreciated.
The text was updated successfully, but these errors were encountered: