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
parsers that look for fixed data like tag, is_not, and similar (generally ones that use the FindToken trait?) should be able to take single u8s so they can be used with byte character literals or for matching precise byte values. Currently impls exist for [u8; 1] which is cumbersome, and &[u8] which means needing to use byte strings, and either dereferencing or casting them (as byte string literals are &[u8; N], for which no impls exist).
The text was updated successfully, but these errors were encountered:
parsers that look for fixed data like
tag
,is_not
, and similar (generally ones that use the FindToken trait?) should be able to take singleu8
s so they can be used with byte character literals or for matching precise byte values. Currently impls exist for[u8; 1]
which is cumbersome, and&[u8]
which means needing to use byte strings, and either dereferencing or casting them (as byte string literals are&[u8; N]
, for which no impls exist).The text was updated successfully, but these errors were encountered: