Support std::string_view & boost::string_view #18
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.
Description
Support both
std::string_view
andboost::string_view
as tokenizer's string type argument for following separators:offset_separator
char_separator
char_delimiters_separator
Due to the
escaped_list_separator
's transformation semantics, we cannot simply usestd::string_view
as return token type. But in the future, I think we can let users to decide the return token type and input type separately instead of bind them together, to supportescaped_list_separator
in some conditions, e.g. tokenizestd::string_view
tostd::string
(s).Changes
assign_or_plus_equal
which does nothing special.assign()
/append()
/clear()
for token object to replace overload operator usages, and provide customization points to users (find candidates via ADL).Note
This pull request is based on #17, please merge it first.