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
I've recently used cats-parse a bit, and in there they split parsers into Parser and Parser0, where Parser0 is reserved for parsers that can succeed without consuming any input.
It wasn't an enjoyable experience figuring out how to use it at first (although that was mostly for Scala reasons than anything else - no typed holes, things being located on companion objects vs object methods, etc.), but I ended up thinking it's a pretty good idea.
This probably relates somewhat to #202, but involves slightly less reimagining.
The text was updated successfully, but these errors were encountered:
I've recently used
cats-parse
a bit, and in there they split parsers intoParser
andParser0
, whereParser0
is reserved for parsers that can succeed without consuming any input.It wasn't an enjoyable experience figuring out how to use it at first (although that was mostly for Scala reasons than anything else - no typed holes, things being located on companion objects vs object methods, etc.), but I ended up thinking it's a pretty good idea.
This probably relates somewhat to #202, but involves slightly less reimagining.
The text was updated successfully, but these errors were encountered: