LUMIERA.clone/tests/library/diff/tree-manipulation-binding-test.cpp

358 lines
16 KiB
C++
Raw Normal View History

/*
TreeManipulationBinding(Test) - techniques to map generic changes to concrete tree shaped data
Copyright (C) Lumiera.org
2016, Hermann Vosseler <Ichthyostega@web.de>
This program 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.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
* *****************************************************/
#include "lib/test/run.hpp"
2015-08-28 23:09:10 +02:00
#include "lib/format-util.hpp"
#include "lib/test/test-helper.hpp"
#include "lib/diff/tree-mutator.hpp"
#include "lib/diff/test-mutation-target.hpp"
#include "lib/time/timevalue.hpp"
#include "lib/format-cout.hpp"
#include "lib/format-util.hpp"
#include "lib/error.hpp"
#include "lib/util.hpp"
//#include <utility>
#include <string>
//#include <vector>
using util::join;
using util::isnil;
using util::contains;
using lib::time::Time;
using std::string;
//using std::vector;
//using std::swap;
using util::typeStr;
settle on a concrete implementation approach based on inheritance chain After some reconsideration, I decide to stick to the approach with the closures, but to use a metaprotramming technique to build an inheritance chain. While I can not decide on the real world impact of storing all those closures, in theory this approach should enable the compiler to remove all of the storage overhead. Since, when storing the result into an auto variable right within scope (as demonstrated in the test), the compiler sees the concrete type and might be able to boil down the actual generated virtual function implementations, thereby inlining the given closures. Whereas, on the other hand, if we'd go the obvious conventional route and place the closures into a Map allocated on the stack, I wouldn't expect the compiler to do data flow analysis to prove this allocation is not necessary and inline it away. NOTE: there is now guarantee this inlining trick will ever work. And, moreover, we don't know anything regarding the runtime effect. The whole picture is way more involved as it might seem at first sight. Even if we go the completely conventional route and require every participating object to supply an implementation of some kind of "Serializable" interface, we'll end up with a (hand written!) implementation class for each participating setup, which takes up space in the code segment of the executable. While the closure based approach chosen here, consumes data segment (or heap) space per instance for the functors (or function pointers) representing the closures, plus code segment space for the closures, but the latter with a way higher potential for inlining, since the closure code and the generated virtual functions are necessarily emitted within the same compilation unit and within a local (inline, not publickly exposed) scope.
2015-04-05 18:26:49 +02:00
namespace lib {
namespace diff{
namespace test{
using lumiera::error::LUMIERA_ERROR_LOGIC;
namespace {//Test fixture....
// define some GenNode elements
// to act as templates within the concrete diff
// NOTE: everything in this diff language is by-value
const GenNode ATTRIB1("α", 1), // attribute α = 1
ATTRIB2("β", int64_t(2)), // attribute α = 2L (int64_t)
ATTRIB3("γ", 3.45), // attribute γ = 3.45 (double)
TYPE_X("type", "ξ"), // a "magic" type attribute "Xi"
TYPE_Z("type", "ζ"), //
CHILD_A("a"), // unnamed string child node
CHILD_B('b'), // unnamed char child node
CHILD_T(Time(12,34,56,78)), // unnamed time value child
SUB_NODE = MakeRec().genNode(), // empty anonymous node used to open a sub scope
ATTRIB_NODE = MakeRec().genNode("δ"), // empty named node to be attached as attribute δ
CHILD_NODE = SUB_NODE, // yet another child node, same ID as SUB_NODE (!)
GAMMA_PI("γ", 3.14159265); // happens to have the same identity (ID) as ATTRIB3AS
}//(End)Test fixture
/********************************************************************************//**
* @test Building blocks to map generic changes to arbitrary private data structures.
* - use a dummy diagnostic implementation to verify the interface
* - integrate the standard case of tree diff application to `Rec<GenNode>`
* - verify an adapter to apply structure modification to a generic collection
* - use closures to translate mutation into manipulation of private attribues
*
* @see TreeMutator
* @see TreeMutator_test
* @see DiffTreeApplication_test
* @see GenNodeBasic_test
* @see AbstractTangible_test::mutate()
*/
class TreeManipulationBinding_test : public Test
{
virtual void
run (Arg)
{
mutateDummy();
mutateGenNode();
mutateCollection();
mutateAttributeMap();
}
/** @test diagnostic binding: how to monitor and verify the mutations applied */
void
mutateDummy()
{
MARK_TEST_FUN;
TestMutationTarget target;
auto mutator =
TreeMutator::build()
.attachDummy (target);
CHECK (isnil (target));
CHECK (mutator.emptySrc());
mutator.injectNew (ATTRIB1);
CHECK (!isnil (target));
CHECK (contains(target.showContent(), "α = 1"));
CHECK (target.verifyEvent("injectNew","α = 1")
.after("attachMutator"));
mutator.injectNew (ATTRIB3);
mutator.injectNew (ATTRIB3);
mutator.injectNew (CHILD_B);
mutator.injectNew (CHILD_B);
mutator.injectNew (CHILD_T);
CHECK (target.verify("attachMutator")
.beforeEvent("injectNew","α = 1")
.beforeEvent("injectNew","γ = 3.45")
.beforeEvent("injectNew","γ = 3.45")
.beforeEvent("injectNew","b")
.beforeEvent("injectNew","b")
.beforeEvent("injectNew","78:56:34.012")
);
CHECK (target.showContent() == "α = 1, γ = 3.45, γ = 3.45, b, b, 78:56:34.012");
cout << "Content after population; "
<< target.showContent() <<endl;
// now attach new mutator for second round...
auto mutator2 =
TreeMutator::build()
.attachDummy (target);
CHECK (target.verify("attachMutator")
.beforeEvent("injectNew","78:56:34.012")
.before("attachMutator"));
CHECK (isnil (target)); // the "visible" new content is still void
2016-03-19 01:42:27 +01:00
CHECK (not mutator2.emptySrc()); // content was moved into hidden "src" buffer
CHECK (target.showSrcBuffer() == "α = 1, γ = 3.45, γ = 3.45, b, b, 78:56:34.012");
CHECK (mutator2.matchSrc (ATTRIB1)); // current head element of src "matches" the given spec
CHECK (isnil (target)); // the match didn't change anything
CHECK (mutator2.findSrc (ATTRIB3)); // serach for an element further down into src... // findSrc
CHECK (!isnil (target)); // ...pick and accept it into the "visible" part of target
CHECK (target.showContent() == "γ = 3.45");
CHECK (mutator2.matchSrc (ATTRIB1)); // element at head of src is still ATTRIB1 (as before)
CHECK (mutator2.acceptSrc (ATTRIB1)); // now pick and accept this src element // acceptSrc
CHECK (target.showContent() == "γ = 3.45, α = 1");
CHECK (not mutator2.emptySrc()); // next we have to clean up waste
mutator2.skipSrc(); // left behind by the findSrc() operation // skipSrc
CHECK (target.showContent() == "γ = 3.45, α = 1");
mutator2.injectNew (ATTRIB2); // injectNew
CHECK (not mutator2.emptySrc());
CHECK (mutator2.matchSrc (ATTRIB3));
CHECK (mutator2.acceptSrc (ATTRIB3)); // acceptSrc
CHECK (target.showContent() == "γ = 3.45, α = 1, β = 2, γ = 3.45");
2016-03-19 01:42:27 +01:00
// now proceeding with the children.
// NOTE: the TestWireTap / TestMutationTarget does not enforce the attribute / children distinction!
CHECK (not mutator2.emptySrc());
CHECK (mutator2.matchSrc (CHILD_B)); // first child waiting in src is CHILD_B
2016-03-19 01:42:27 +01:00
mutator2.skipSrc(); // ...which will be skipped (and thus discarded // skipSrc
mutator2.injectNew (SUB_NODE); // inject a new nested sub-structure here // injectNew
CHECK (mutator2.matchSrc (CHILD_B)); // yet another B-child is waiting
CHECK (not mutator2.findSrc (CHILD_A)); // unsuccessful find operation won't do anything
CHECK (not mutator2.emptySrc());
CHECK (mutator2.matchSrc (CHILD_B)); // child B still waiting, unaffected
CHECK (not mutator2.acceptSrc (CHILD_T)); // refusing to accept/pick a non matching element
CHECK (mutator2.matchSrc (CHILD_B)); // child B still patiently waiting, unaffected
CHECK (mutator2.acceptSrc (CHILD_B)); // acceptSrc
CHECK (mutator2.matchSrc (CHILD_T));
CHECK (mutator2.acceptSrc (CHILD_T)); // acceptSrc
CHECK (mutator2.emptySrc()); // source contents exhausted
CHECK (not mutator2.acceptSrc (CHILD_T));
CHECK (target.verify("attachMutator")
.beforeEvent("injectNew","78:56:34.012")
.before("attachMutator")
.beforeEvent("findSrc","γ = 3.45")
.beforeEvent("acceptSrc","α = 1")
.beforeEvent("skipSrc","")
.beforeEvent("injectNew","β = 2")
.beforeEvent("acceptSrc","γ = 3.45")
.beforeEvent("skipSrc","b")
.beforeEvent("injectNew","Rec()")
.beforeEvent("acceptSrc","b")
.beforeEvent("acceptSrc","78:56:34.012")
);
CHECK (target.showContent() == "γ = 3.45, α = 1, β = 2, γ = 3.45, Rec(), b, 78:56:34.012");
cout << "Content after reordering; "
<< target.showContent() <<endl;
// the third round will cover tree mutation primitives...
auto mutator3 =
TreeMutator::build()
.attachDummy (target);
CHECK (isnil (target));
CHECK (mutator3.matchSrc (ATTRIB3)); // new mutator starts out anew at the beginning
CHECK (mutator3.accept_until (ATTRIB2)); // fast forward behind attribute β
CHECK (mutator3.acceptSrc (ATTRIB3)); // and accept the second copy of attribute γ
CHECK (mutator3.matchSrc (SUB_NODE)); // this /would/ be the next source element, but...
CHECK (not contains(target.showContent(), "γ = 3.1415927"));
CHECK (mutator3.assignElm(GAMMA_PI)); // ...we assign a new payload to the current element first
CHECK ( contains(target.showContent(), "γ = 3.1415927"));
CHECK (mutator3.accept_until (Ref::END)); // fast forward, since we do not want to re-order anything
cout << "Content after assignment; "
<< target.showContent() <<endl;
// for mutation of an enclosed scope, in real usage the managing TreeDiffInterpreter
// would maintain a stack of "mutation frames", where each one provides an OpaqueHolder
// to place a suitable sub-mutator for this nested scope. At this point, we can't get any further
// with this TestWireTap / TestMutationTarget approach, since the latter just records actions and
// otherwise forwards operation to the rest of the TreeMutator. In case there is no /real/ mutator
// in any "onion layer" below the TestWireTap within this TreeMutator, we'll just get a default (NOP)
// implementation of TreeMutator without any further functionality.
InPlaceBuffer<TreeMutator, sizeof(mutator3)> subMutatorBuffer;
TreeMutator::MutatorBuffer placementHandle(subMutatorBuffer);
CHECK (mutator3.mutateChild (SUB_NODE, placementHandle));
CHECK (subMutatorBuffer->emptySrc()); // ...this is all we can do here
// the real implementation would instead find a suitable
// sub-mutator within this buffer and recurse into that.
// error handling: assignment might throw
GenNode differentTime{CHILD_T.idi.getSym(), Time(11,22)};
VERIFY_ERROR (LOGIC, mutator3.assignElm (differentTime));
CHECK (target.showContent() == "γ = 3.45, α = 1, β = 2, γ = 3.1415927, Rec(), b, 78:56:34.012");
CHECK (target.verifyEvent("acceptSrc","78:56:34.012")
.before("attachMutator TestWireTap")
.beforeEvent("accept_until β","γ = 3.45")
.beforeEvent("accept_until β","α = 1")
.beforeEvent("accept_until β","β = 2")
.beforeEvent("acceptSrc","γ = 3.45")
.beforeEvent("assignElm","γ: 3.45 ⤅ 3.1415927")
.beforeEvent("accept_until END","Rec()")
.beforeEvent("accept_until END","b")
.beforeEvent("accept_until END","78:56:34.012")
.beforeEvent("mutateChild","_CHILD_Record.001: start mutation...Rec()")
);
cout << "____Mutation-Log______________\n"
<< join(target.getLog(), "\n")
<< "\n───╼━━━━━━━━━╾────────────────"<<endl;
}
/** @test map mutation primitives onto a STL collection managed locally. */
void
2016-03-19 01:42:27 +01:00
mutateCollection()
{
MARK_TEST_FUN;
// some private data structures
struct Data
{
string key;
string val;
operator string() const { return _Fmt{"≺%s%s≻"} % key % val; }
bool operator== (Data const& o) const { return key==o.key and val==o.val; }
bool operator!= (Data const& o) const { return not (*this == o); }
};
using VecD = std::vector<Data>;
using MapD = std::map<string, VecD>;
VecD target;
// now set up a binding to these opaque private structures...
auto mutator =
TreeMutator::build()
.attach (collection(target)
.constructFrom ([&](GenNode const& spec) -> Data
{
cout << "constructor invoked on "<<spec<<endl;
return {spec.idi.getSym(), render(spec.data)};
})
.matchElement ([&](GenNode const& spec, Data const& elm)
{
cout << "match? "<<spec.idi.getSym()<<"=?="<<elm.key<<endl;
return spec.idi.getSym() == elm.key;
})
);
cout << lib::test::showSizeof(mutator) <<endl;
// --- first round: populate the collection ---
CHECK (isnil (target));
CHECK (mutator.emptySrc());
mutator.injectNew (ATTRIB1);
CHECK (!isnil (target));
cout << "inject..." << join(target) <<endl;
CHECK (contains(join(target), "α1≻"));
mutator.injectNew (ATTRIB3);
mutator.injectNew (ATTRIB3);
mutator.injectNew (CHILD_B);
mutator.injectNew (CHILD_B);
mutator.injectNew (CHILD_T);
cout << "inject......" << join(target) <<endl;
}
void
2016-03-19 01:42:27 +01:00
mutateAttributeMap ()
{
2016-03-19 01:42:27 +01:00
TODO ("define how to translate generic mutation into attribute manipulation");
}
void
2016-03-19 01:42:27 +01:00
mutateGenNode()
{
2016-03-19 01:42:27 +01:00
TODO ("define how to fit GenNode tree mutation into the framework");
}
};
/** Register this test class... */
LAUNCHER (TreeManipulationBinding_test, "unit common");
}}} // namespace lib::diff::test