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
In nom 8.0, there is a new way of writing parsers using a Parser trait. Some of nom's parsers are now written using this Parser trait, and some using the older function syntax.
In nom::character::complete and nom::character::streaming, there are many parsers:
alpha0
alpha1
digit0
digit1
newline
etc
These all seem to be written using the old function syntax. For example:
But notably many of the parsers from the complete and streaming modules like digit0, alpha0, alpha1, etc are missing. For example this module has a digit1 but not a digit0.
So as a user, it's unclear when parsers should be used from the parent nom::character or the child complete/streaming. And it's also not clear why nom::character is missing so many compared to complete/streaming. I think this could be documented better.
The text was updated successfully, but these errors were encountered:
In nom 8.0, there is a new way of writing parsers using a
Parser
trait. Some of nom's parsers are now written using thisParser
trait, and some using the older function syntax.In
nom::character::complete
andnom::character::streaming
, there are many parsers:alpha0
alpha1
digit0
digit1
newline
These all seem to be written using the old function syntax. For example:
In
nom::character
, there are a small subset of these parsers:digit1
char
These seem to be written using the new
Parser
trait. For example:But notably many of the parsers from the
complete
andstreaming
modules likedigit0
,alpha0
,alpha1
, etc are missing. For example this module has adigit1
but not adigit0
.So as a user, it's unclear when parsers should be used from the parent
nom::character
or the childcomplete
/streaming
. And it's also not clear whynom::character
is missing so many compared tocomplete
/streaming
. I think this could be documented better.The text was updated successfully, but these errors were encountered: