A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://en.cppreference.com/w/cpp/language/../named_req/ForwardIterator.html below:

C++ named requirements: LegacyForwardIterator - cppreference.com

A LegacyForwardIterator is a LegacyIterator that can read data from the pointed-to element.

Unlike LegacyInputIterator and LegacyOutputIterator, it can be used in multipass algorithms.

If a LegacyForwardIterator it originates from a Container, then it's value type is the same as the container's, so dereferencing (*it) obtains the container's value type.

[edit] Requirements

X satisfies LegacyForwardIterator if all following conditions are satisfied:

 Expression  Type Effects r++ convertible to const X&  Equivalent to X x = r;
++r;
return x;
. *i++ Ref [edit] Equality domain

The domain of == for forward iterators is that of iterators over the same underlying sequence.

However, value-initialized forward iterators can be compared, and must compare equal to other value-initialized iterators of the same type.

In other words, value-initialized forward iterators behave as if they refer past the end of the same empty sequence.

(since C++14) [edit] Multi-pass guarantee

Two dereferenceable iterators a and b of type X offer the multi-pass guarantee if all following conditions are satisfied:

Concept

For the definition of std::iterator_traits, the following exposition-only concept is defined.

where the exposition-only concept __LegacyInputIterator<T> is described in LegacyInputIterator.

(since C++20) [edit] Notes

Unlike the std::forward_iterator concept, the LegacyForwardIterator requirements requires dereference to return a reference.

[edit] Defect reports

The following behavior-changing defect reports were applied retroactively to previously published C++ standards.

DR Applied to Behavior as published Correct behavior LWG 1212
(N3066) C++98 the type of *i++ did not match the type of
*i-- required by LegacyBidirectionalIterator changed the
type to Ref LWG 1311
(N3066) C++98 “a == b implies ++a == ++b” alone
did not offer multipass guarantee[1] also requires “a == b
implies ++a != b”[2] LWG 3798 C++20 __LegacyForwardIterator required
std::iter_reference_t<It> to be an lvalue reference type also allows rvalue
reference types
  1. ↑ In the scenario where a and b use the same underlying iterator, evaluating the expression ++a == ++b actually increments the underlying container twice, but the result is still true.
  2. ↑ Formally also requires implying ++b != a.
[edit] See also

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4