forked from boostorg/range
[boost][range] - Trac 5971 - size() should return an unsigned type.
[SVN r77990]
This commit is contained in:
@@ -13,7 +13,7 @@ Since ranges are characterized by a specific underlying iterator type, we get a
|
||||
* Readable Range
|
||||
* Writeable Range
|
||||
* Swappable Range
|
||||
* Lvalue Range
|
||||
* Lvalue Range
|
||||
* [*/Traversal/] category:
|
||||
* __single_pass_range__
|
||||
* __forward_range__
|
||||
@@ -25,7 +25,7 @@ Notice how we have used the categories from the __new_style_iterators__.
|
||||
Notice that an iterator (and therefore an range) has one [*/traversal/] property and one or more properties from the [*/value access/] category. So in reality we will mostly talk about mixtures such as
|
||||
|
||||
* Random Access Readable Writeable Range
|
||||
* Forward Lvalue Range
|
||||
* Forward Lvalue Range
|
||||
|
||||
By convention, we should always specify the [*/traversal/] property first as done above. This seems reasonable since there will only be one [*/traversal/] property, but perhaps many [*/value access/] properties.
|
||||
|
||||
@@ -37,7 +37,7 @@ As another example, consider how we specify the interface of `std::sort()`. Algo
|
||||
template< class RandomAccessTraversalReadableWritableIterator >
|
||||
void sort( RandomAccessTraversalReadableWritableIterator first,
|
||||
RandomAccessTraversalReadableWritableIterator last );
|
||||
``
|
||||
``
|
||||
|
||||
For ranges the interface becomes
|
||||
|
||||
@@ -45,6 +45,6 @@ For ranges the interface becomes
|
||||
template< class RandomAccessReadableWritableRange >
|
||||
void sort( RandomAccessReadableWritableRange& r );
|
||||
``
|
||||
|
||||
|
||||
[endsect]
|
||||
|
||||
|
Reference in New Issue
Block a user