Open poyenc opened 4 years ago
Merging #18 into develop will increase coverage by
17.72%
. The diff coverage is87.80%
.
@@ Coverage Diff @@
## develop #18 +/- ##
============================================
+ Coverage 70.95% 88.67% +17.72%
============================================
Files 3 3
Lines 210 212 +2
Branches 74 64 -10
============================================
+ Hits 149 188 +39
+ Misses 18 0 -18
+ Partials 43 24 -19
Impacted Files | Coverage Δ | |
---|---|---|
include/boost/token_functions.hpp | 88.88% <87.50%> (+17.70%) |
:arrow_up: |
include/boost/token_iterator.hpp | 88.46% <100.00%> (+18.09%) |
:arrow_up: |
include/boost/tokenizer.hpp | 83.33% <0.00%> (+16.66%) |
:arrow_up: |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 1c8a8bf...6a3c01b. Read the comment docs.
need to figure out why we have coverage drop
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.