A variant of Apply() that works with any TextParser<TextSpan> #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While working through #32 I couldn't find an idiomatic/allocation-free way for a text parser to break up a number like
20180521
into numeric parts. This led me to a bit of a general pattern, like this:This variant of
Apply()
makes it possible to split the tasks of delimiting the span to be parsed (Span.Length(2)
) from its translation into the value type (here, taking12
and parsing anint
).Not sure how frequently this will get used - definitely quite pleasant for length-oriented formats like this one - but it's a nice complement to the existing token-oriented
Apply()
combinator, so might prove fruitful and/or stimulating to include.