Opened 12 years ago
Closed 12 years ago
#4451 closed Bugs (fixed)
reverse_range naming is not consistent with other range adaptors
Reported by: | Mathias Gaunard | Owned by: | Neil Groves |
---|---|---|---|
Milestone: | Boost 1.46.0 | Component: | range |
Version: | Boost 1.44.0 | Severity: | Problem |
Keywords: | Cc: | Neil Groves |
Description
Other range adaptors are named joined_range, indexed_range, replaced_range, etc.
reverse_range should thus be named reversed_range for consistency.
Change History (2)
comment:1 by , 12 years ago
Status: | new → assigned |
---|
comment:2 by , 12 years ago
Milestone: | Boost 1.44.0 → Boost 1.46.0 |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Resolved on the trunk. The ranges returned by the range adaptors have had the names made consistent and the return types added to the documentation.