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
Currently, zero-copy differentiates between select! and select_ref!: the former selects upon tokens by-value, the other by-ref.
The former is required for inputs that do not implement BorrowInput (i.e: those from which tokens cannot be borrowed, such as char from &str or T from Stream<T>), while the latter is required for cases where a reference to the original input is required (such as for parsing nested inputs).
It would be nice to unify these two cases into a single macro, ideally without requiring users to understand the intricate details.
The text was updated successfully, but these errors were encountered:
zesterer
added
api
A problem with the design of an API feature
1.0
Features that should be implemented for the 1.0 release
labels
Mar 1, 2023
Currently,
zero-copy
differentiates betweenselect!
andselect_ref!
: the former selects upon tokens by-value, the other by-ref.The former is required for inputs that do not implement
BorrowInput
(i.e: those from which tokens cannot be borrowed, such aschar
from&str
orT
fromStream<T>
), while the latter is required for cases where a reference to the original input is required (such as for parsing nested inputs).It would be nice to unify these two cases into a single macro, ideally without requiring users to understand the intricate details.
The text was updated successfully, but these errors were encountered: