opened
LiamGoodacre
username_0
Add Alternative instance for ParseT?
issue
created
hdgarrood
username_1
:+1:
comment
created
LiamGoodacre
username_0
-- use monoid, combine errors?
-- Simply take rightmost?
-- Or maybe take the one with the deepest path?
--
-- Or, export our own (<|>) that uses a semigroup (since errors are
-- 'nonempty') - that is, we don't want to allow failing with no error.

Given the reasoning of the last bit, should I try that instead?
comment
created
hdgarrood
username_1
Ha, it was such a long time ago that I wrote that, I'd completely forgotten. Come to think of it I'm not sure how we could provide a way of combining errors, other than by returning a list of `ParseError`, and I don't think I want to do that, as it seems unnecessarily complex. Having `Alternative` would be nice but I think I'd rather provide a monomorphic `<|>` function, since there's no good definition for the `empty` class method from `Alternative`. I think my favourite approach would be to take the right side's error if both parsers error, what do you think?
comment
closed
hdgarrood
username_1
issue
created
hdgarrood
username_1
Resolved by #11.
comment