Opened 9 years ago
Closed 9 years ago
#8594 closed Bugs (fixed)
range_return utterly undocumented
| Reported by: | Dave Abrahams | Owned by: | Neil Groves |
|---|---|---|---|
| Milestone: | Boost 1.56.0 | Component: | range |
| Version: | Boost 1.53.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
This component is fundamental to many of the library's interfaces, right? Shouldn't there be something in the docs about what it is or what it does!?
Change History (5)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Status: | new → assigned |
|---|
comment:3 by , 9 years ago
| Milestone: | Boost 1.54.0 → Boost 1.56.0 |
|---|
comment:4 by , 9 years ago
This wasn't mentioned by name, but the usage was documented in the algorithms.qbk with boost::unique used as example. I shall mention the range_return by name to make it easier to search for.
comment:5 by , 9 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
You are right, this isn't documented and should be.