[ San Francisco: ]

NAD Editorial, see N2777.

Proposed resolution:

In [move.iterator] and [move.iter.op.index], change the declaration of move_iterator's operator[] to:

reference unspecified operator[](difference_type n) const;

[ 2009-10 Santa Cruz: ]

Move to Ready. Note that if 1051 is reopened, it may yield a better resolution, but 1051 is currently marked NAD.

[ 2009-08-15 Howard adds: ]

I recommend closing this as a duplicate of 1051 which addresses this issue for both move_iterator and reverse_iterator.

[ 2009-07-28 Reopened by Alisdair. No longer solved by concepts. ]

move_iterator's operator[] is declared as:

reference operator[](difference_type n) const;

This has the same problem that reverse_iterator's operator[] used to have: if the underlying iterator's operator[] returns a proxy, the implicit conversion to value_type&& could end up referencing a temporary that has already been destroyed. This is essentially the same issue that we dealt with for reverse_iterator in DR 386.