Description

Test:: cover the concept of a »state core«, which is used in Lumiera for various aspects of data generation and iteration.

Definition at line 94 of file iter-core-adapter-test.cpp.

Private Types
template<typename T1 , typename T2 >
using	Common = meta::CommonResultYield< T1, T2 >

Member Function Documentation

void simpleUsage ( )

inlineprivate

Test:: build a »Lumiera Forward Iterator« to transition a State-Core towards it final state.

void stateManipulation ( )

inlineprivate

void checked_and_protected ( )

inlineprivate

Test:: additional wrappers to add safety checks or to encapsulate the state core altogether

void value_and_reference_yield ( )

inlineprivate

adapters can (transparently) handle a core which yields values

the decorated core here yields by-value, not by-ref.
Both CheckedCore and IterableDecorator can cope with that
the result is then also delivered by-value from the iterator.
Remarks
the »Lumiera Forward Iterator« concept does not exactly specify what to expect when dereferencing an iterator; yet for obvious reasons, most iterators in practice expose a reference to some underlying container or internal engine state, since this is more or less the whole point of using an iterator: we want to expose something for manipulation, without revealing what it actually is (even while in most cases the implementation is visible for the compiler, the code using the iterator is not tightly coupled). This scheme has ramifications for the way any iterator pipeline works; notably any transformation will have to capture a function result. However, sometimes an iterator can only return a computed value; such an usage can be valid and acceptable and is supported to the degree possible.

Here is the call graph for this function: