lumiera_documentation/tests/lib/iter-core-adapter-test.cpp
Ichthyostega 0760525ea5 Library: deep dive into type reconciliation and tuple handling
This commit is the aggregated result of extended research
that is only loosely related to current development topics.

One theme was the construction of nested data structures using tuples,
which faces some difficulties due to tuple manipulations being limited
almost entirely to compile-time processing. However, the barrier between
compile-time and runtime can be overcome with the help of a dispatcher
table -- which leads to the secondary problem to handle the diverse
tuple elements with a common, generic functor. Such a functor can be
constructed, if and only if those element types are ''reconcilable''

The STDLIB provides two metafunctions, `std::common_type` and
`std::common_refernce`, which however pose some challenges for the
task at hand, since they include additional processing. In the end,
a custom version of the ''basic type reconciliation'' was implemented
and tested, and then used as foundation to build a dispatcher table
for runtime-indexed access and iteration over tuples.

As an aside, several deeply hidden bugs in our library code were resolved,
and the tuple-helpers, tuple string rendering and associated utilities
were regrouped and modernised.

As result of this research work, the following components are provided:
- meta/common-result
- meta/fun-trampoline
- meta/tuple-index-adaptor
2026-04-07 06:32:23 +02:00

258 lines
7.3 KiB
C++
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

/*
IterCoreAdapter(Test) - iterating over a »state core«
Copyright (C)
2024, Hermann Vosseler <Ichthyostega@web.de>
  **Lumiera** is free software; you can redistribute it and/or modify it
  under the terms of the GNU General Public License as published by the
  Free Software Foundation; either version 2 of the License, or (at your
  option) any later version. See the file COPYING for further details.
* *****************************************************************/
/** @file iter-core-adapter-test.cpp
** unit test \ref IterCoreAdapter_test
*/
#include "test/run.hpp"
#include "test/test-helper.hpp"
#include "lib/util.hpp"
#include "lib/iter-adapter.hpp"
#include "lib/meta/common-result.hpp"
#include <string>
using LERR_(ITER_EXHAUST);
using util::isSameObject;
using test::showType;
using std::string;
namespace lib {
namespace test{
namespace { // Test fixture
/**
* A test »**State Core**« which steps down a number to zero.
* @note this is a minimal description of a state progression towards a goal
* - default constructed is equivalent to _goal was reached_
* - can be copied, manipulated and compared
* - yields reference to internal state
* - no safety checks whatsoever
*/
struct StepDown
{
uint n;
StepDown (uint start =0)
: n{start}
{ }
bool
checkPoint() const
{
return n != 0;
}
uint&
yield() const
{
return util::unConst(n);
}
void
iterNext()
{
--n;
}
bool
operator== (StepDown const& o) const
{
return n == o.n;
}
};
}// (END) test dummy
/*****************************************************************//**
* @test cover the concept of a »state core«, which is used in Lumiera
* for various aspects of data generation and iteration.
* @see IterStateWrapper
* @see iter-adapter.hpp
* @see iter-explorer.hpp
*/
class IterCoreAdapter_test : public Test
{
virtual void
run (Arg)
{
simpleUsage();
stateManipulation();
checked_and_protected();
value_and_reference_yield();
verify_TypeReconciliation();
}
/** @test build a »Lumiera Forward Iterator«
* to transition a State-Core towards it final state.
*/
void
simpleUsage()
{
auto it = IterableDecorator<StepDown>{3};
CHECK (it);
CHECK (*it == 3);
++it;
CHECK (it);
CHECK (*it == 2);
++it;
CHECK (it);
CHECK (*it == 1);
++it;
CHECK (not it);
}
/** @test state of a decorated un-checked core can be manipulated */
void
stateManipulation()
{
auto it = IterableDecorator<StepDown>{};
CHECK (not it);
CHECK (*it == 0);
++it;
CHECK (*it == uint(-1));
CHECK (it);
*it = 5;
CHECK (*it == 5);
++it;
CHECK (*it == 4);
it.n = 1;
CHECK (*it == 1);
CHECK (it);
++it;
CHECK (not it);
CHECK (it.n == 0);
CHECK (isSameObject(*it, it.n));
}
/** @test additional wrappers to add safety checks
* or to encapsulate the state core altogether */
void
checked_and_protected()
{
auto cc = CheckedCore<StepDown>{2};
CHECK (cc.checkPoint());
CHECK (cc.yield() == 2u);
cc.n = 1;
CHECK (cc.yield() == 1u);
cc.iterNext();
CHECK (not cc.checkPoint());
CHECK (cc.n == 0u);
VERIFY_ERROR (ITER_EXHAUST, cc.yield() );
VERIFY_ERROR (ITER_EXHAUST, cc.iterNext() );
auto it = IterStateWrapper{StepDown{2}};
CHECK (it);
CHECK (*it == 2u);
++it;
CHECK (*it == 1u);
++it;
CHECK (not it);
VERIFY_ERROR (ITER_EXHAUST, *it );
VERIFY_ERROR (ITER_EXHAUST, ++it );
}
/** @test adapters can (transparently) handle a core which yields values
* - demonstrate how cores can be augmented by decoration...
* - 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.
* @remark 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.
*/
void
value_and_reference_yield ()
{
struct ValueStep
: StepDown
{
using StepDown::StepDown;
int yield() const { return StepDown::yield(); }
};
auto it = IterableDecorator<CheckedCore<ValueStep>>{2};
CHECK (it);
CHECK (*it == 2);
CHECK (it.n == 2);
CHECK (not isSameObject(*it, it.n));
CHECK (showType<decltype(*it)>() == "int"_expect);
StepDown& ix{it};
CHECK (ix.yield() == 2u);
CHECK ( isSameObject(ix.yield(), ix.n));
CHECK ( isSameObject(ix.yield(), it.n));
CHECK (showType<decltype(ix.yield())>() == "uint&"_expect);
++it;
CHECK (*it == 1);
++it;
VERIFY_ERROR (ITER_EXHAUST, *it );
VERIFY_ERROR (ITER_EXHAUST, ++it );
}
/** @test when combining functors, a common result type can be detected.
* @see CommonResult_test
* @see lib/meta/common-result.hpp
*/
void
verify_TypeReconciliation()
{
using C1 = meta::CommonResult<int,string>;
CHECK (not C1{});
CHECK (not C1::value);
using C2 = Common<string&,string>;
CHECK (showType<C2::Type>() == "string"_expect );
using C3 = Common<double&, long const&>;
CHECK (showType<C3::Type>() == "double"_expect ); // usual in C++ (loss of precision possible)
}
template<typename T1, typename T2>
using Common = meta::CommonResult<T1,T2>;
};
LAUNCHER (IterCoreAdapter_test, "unit common");
}} // namespace lib::test