lumiera_/src/lib/meta/function-erasure.hpp

214 lines
6.5 KiB
C++

/*
FUNCTION-ERASURE.hpp - wrapping a functor object for inline storage while hiding the signature
Copyright (C) Lumiera.org
2009, 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.
*/
/** @file function-erasure.hpp
** Generic holder for functor objects, concealing the concrete function type.
** When working with generic function objects and function pointers typed to
** arbitrary signatures, often there is the necessity to hold onto such a functor
** while hiding the actual signature behind an common interface ("type erasure").
** The usual solution based on subclassing has the downside of requiring separate
** storage for the concrete functor object, which might become problematic when
** dealing with lots of functor objects.
**
** Especially when dealing with std::function objects, all of the type differences
** are actually encoded into 3 internal pointers, thus yielding the same size for
** all various types of functors. Building on this observation, we can create an
** common container object to store the varying functors inline, while hiding the
** actual signature.
**
** There remains the problem of re-accessing the concrete functor later on. As
** C++ has only rudimental introspection capabilities, we can only rely on the
** usage context to provide the correct function signature; only when using a
** virtual function for the re-access, we can perform at least a runtime-check.
**
** Thus there are various flavours for actually implementing this idea, and
** picking a suitable implementation depends largely on the context. Thus we
** provide a common frontend for access and expect the client code to pick
** a suitable implementation policy.
**
** @see control::Mutation usage example
** @see function-erasure-test.cpp
**
*/
#ifndef LIB_META_FUNCTION_ERASURE_H
#define LIB_META_FUNCTION_ERASURE_H
#include "lib/util.hpp"
#include "lib/error.hpp"
#include "lib/opaque-holder.hpp"
#include <functional>
namespace lib {
namespace meta{
using std::function;
using util::unConst;
/**************************************************//**
* Generic wrapper carrying a function object
* while hiding the actual function signature
* - create it using a function ref or pointer
* - the StoreFunction-policy also allows
* creation based on an existing function object
* - re-access the functor or function ref
* using the templated \c getFun()
*
* @param FH policy to control the implementation.
* In most cases, you should use "StoreFunction"
* @note not statically typesafe. Depending on
* the specified policy, it \em might be
* run-time typesafe.
*/
template<class FH>
struct FunErasure
: FH
{
template<typename FUN>
FunErasure (FUN const& functor)
: FH(functor)
{ }
friend bool
operator!= (FunErasure const& fer1, FunErasure const& fer2)
{
return not (fer1==fer2); // use equality defined by FH
}
};
/* ====== Policy classes ====== */
typedef function<void(void)> FunVoid;
typedef lib::InPlaceAnyHolder< sizeof(FunVoid) // same size for all function objects
, lib::InPlaceAnyHolder_unrelatedTypes // no common base class!
> FunHolder;
typedef lib::InPlaceAnyHolder< sizeof(void*)
, lib::InPlaceAnyHolder_unrelatedTypes
> FunPtrHolder;
/**
* Policy for FunErasure: store an embedded std::function
* Using this policy allows to store arbitrary complex functor objects
* embedded within a neutral container and retrieving them later type-safe.
* The price to pay is vtable access and heap storage of function arguments.
*/
class StoreFunction
: public FunHolder
{
public:
template<typename SIG>
StoreFunction (SIG& fun)
: FunHolder(function<SIG>(fun))
{ }
template<typename SIG>
StoreFunction (function<SIG> const& fun)
: FunHolder(fun)
{ }
template<typename SIG>
function<SIG>&
getFun () const
{
return get<function<SIG>>();
}
};
/**
* Policy for FunErasure: store a bare function pointer.
* Using this policy allows to store a conventional function ptr,
* while still being able to re-access it later with run-time type check.
* The price to pay is vtable access.
*/
class StoreFunPtr
: public FunPtrHolder
{
public:
template<typename SIG>
StoreFunPtr (SIG& fun)
: FunPtrHolder(&fun)
{ }
template<typename SIG>
StoreFunPtr (SIG *fun)
: FunPtrHolder(fun)
{ }
template<typename SIG>
SIG&
getFun () const
{
SIG *fun = get<SIG*>();
REQUIRE (fun);
return *fun;
}
};
/**
* Policy for FunErasure: store an unchecked bare function pointer.
* Using this policy allows to store a conventional function ptr,
* and to retrieve it without overhead, but also without safety.
*/
class StoreUncheckedFunPtr
{
void *funP_;
public:
template<typename SIG>
StoreUncheckedFunPtr (SIG& fun)
{
funP_ = reinterpret_cast<void*> (&fun);
}
template<typename SIG>
StoreUncheckedFunPtr (SIG *fun)
{
funP_ = reinterpret_cast<void*> (fun);
}
template<typename SIG>
SIG&
getFun ()
{
return *reinterpret_cast<SIG*> (funP_);
}
explicit operator bool() const { return funP_; }
bool isValid() const { return funP_; }
};
}} // namespace lib::meta
#endif