boost/parser
2
0
Fork 0
mirror of https://github.com/boostorg/parser.git synced 2026-01-19 04:22:13 +00:00
Code Issues Projects Releases Wiki Activity

Call out the constraint on the ReplacementV template parameter to replace().

Browse Source 
Partially addresses #97.
This commit is contained in:
Zach Laine
2024-02-19 21:33:47 -06:00
parent 4ff205d6ec
commit 0ea1516b6e
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/tutorial.qbk
View File

@@ -3014,6 +3014,10 @@ similar.
[section Algorithms and Views That Use Parsers]
Unless otherwise noted, all the algorithms and views are constrained very much
like the way the _p_ overloads are. The kinds of ranges, parsers, etc., that
they accept are the same.
[heading _search_]
As shown in _p_api_, the two patterns of parsing in _Parser_ are whole-parse
@@ -3184,6 +3188,11 @@ is because the subranges produced are all common ranges, and so if
pass very long C-style strings to _replace_ and not pay to see the end until
the range is used, don't.
`ReplacementV` is constrained almost exactly the same as `V`. `V` must model
`parsable_range` and `std::ranges::viewable_range`. `ReplacementV` is the
same, except that it can also be a `std::ranges::input_range`, whereas `V`
must be a `std::ranges::forward_range`.
You may wonder what happens when you pass a UTF-N range for `r`, and a UTF-M
range for `replacement`. What happens in this case is silent transcoding of
`replacement` from UTF-M to UTF-N by the _replace_ range adaptor. This