boostorg/iterator
1
0
Fork 1
mirror of https://github.com/boostorg/iterator.git synced 2025-07-30 21:07:20 +02:00
Code Issues Packages Projects Releases Wiki Activity

added more rationale to the operator-> issue

Browse Source 
[SVN r21739]
This commit is contained in:
Jeremy Siek
2004-01-14 20:29:51 +00:00
parent 2854c5c761
commit 42147b9e86
1 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
doc/iter-issue-list.rst
View File

@ -952,8 +952,17 @@ instead of ``(*a).m`` ?
:Proposed resolution: NAD. :Proposed resolution: NAD.
:Rationale: We think you're misreading "pre:". :Rationale: We think you're misreading "pre:".
Also requiring proxy iterators to support ``->`` would make old If ``(*a).m`` is not well defined, then the iterator is not
iterators not conform to new iterator requirements. required to provide ``a->m``. So a proxy iterator is not
required to provide ``a->m``.
As an aside, it is possible for proxy iterators to
support ``->``, so changing the requirements to
read ``static_cast<T>(*a).m`` is interesting.
However, such a change to Readable Iterator would
mean that it no longer corresponds to the
input iterator requirements. So old iterators would not necessarily
conform to new iterator requirements.
counting_iterator Traversal argument unspecified counting_iterator Traversal argument unspecified