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
Should consider implementing a Parser as a template with injected Parsers, so that must be a Superpower unit easily combined with other parsers. This is expected to be possible with custom interpolated string handlers and might look like the following:
I failed to figure out how I can make it infer the type from the formatted parsers values, basically because overloads cannot differ only by their return types. The type correspondence can be controlled by a dedicated Roslyn analyzer, though.
Consider the following input from day 14 of year 2024
A Superpower parser with some already implemented extensions might look like the following:
Still a lot for a relatively simple input.
Should consider implementing a Parser as a template with injected Parsers, so that must be a Superpower unit easily combined with other parsers. This is expected to be possible with custom interpolated string handlers and might look like the following:
I'm not happy with the tuple stuff though, but some extensions should help with it.
The text was updated successfully, but these errors were encountered: