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
Whenever the select! parser returns an ExpectedFound error, it makes the expected field empty.
I think this has to do with tokens that contains values like:
enumToken{Integer(u64),
...
}
The text was updated successfully, but these errors were encountered:
Yep, this is because chumsky has no way of understanding what select! is trying to expect. Right now, an empty expected field should be interpreted as 'something else'. If you want to give it a particular value, I recommend using .labelled(...), which allows you to annotate parser patterns with explicit labels and have them appear in the expected list (for example, 'expected expression').
In the future we're planning to add more ways to automatically produce better error information.
Whenever the
select!
parser returns anExpectedFound
error, it makes theexpected
field empty.I think this has to do with tokens that contains values like:
The text was updated successfully, but these errors were encountered: