* Lumiera source code always was copyrighted by individual contributors * there is no entity "Lumiera.org" which holds any copyrights * Lumiera source code is provided under the GPL Version 2+ == Explanations == Lumiera as a whole is distributed under Copyleft, GNU General Public License Version 2 or above. For this to become legally effective, the ''File COPYING in the root directory is sufficient.'' The licensing header in each file is not strictly necessary, yet considered good practice; attaching a licence notice increases the likeliness that this information is retained in case someone extracts individual code files. However, it is not by the presence of some text, that legally binding licensing terms become effective; rather the fact matters that a given piece of code was provably copyrighted and published under a license. Even reformatting the code, renaming some variables or deleting parts of the code will not alter this legal situation, but rather creates a derivative work, which is likewise covered by the GPL! The most relevant information in the file header is the notice regarding the time of the first individual copyright claim. By virtue of this initial copyright, the first author is entitled to choose the terms of licensing. All further modifications are permitted and covered by the License. The specific wording or format of the copyright header is not legally relevant, as long as the intention to publish under the GPL remains clear. The extended wording was based on a recommendation by the FSF. It can be shortened, because the full terms of the license are provided alongside the distribution, in the file COPYING.
87 lines
2.8 KiB
C++
87 lines
2.8 KiB
C++
/*
|
||
UTIL-TUPLE.hpp - helpers and convenience shortcuts for working with tuples
|
||
|
||
Copyright (C)
|
||
2023, 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 util-tuples.hpp
|
||
** Some small helpers and convenience shortcuts to simplify working with
|
||
** tuples and sequences (given by iterator). While tuples and sequences
|
||
** are fundamentally different insofar a tuple has a fixed structure (and
|
||
** may hold elements of different type), sometimes it can be convenient to
|
||
** treat a tuple like a sequence (especially a tuple holding elements of a
|
||
** single type. Notably, an iterator can be unloaded into a fixed-size tuple,
|
||
** which in turn can than be used in a structural binding to unpack references
|
||
** to the elements into scoped variables. Obviously, the meaning of the elements
|
||
** in the sequence must be fixed and predetermined -- which is often the case
|
||
** when dealing with tests or communication protocols.
|
||
**
|
||
** @see util-tuple-test.cpp
|
||
** @see util-coll.hpp
|
||
**
|
||
*/
|
||
|
||
|
||
#ifndef UTIL_TUPLE_H
|
||
#define UTIL_TUPLE_H
|
||
|
||
|
||
#include <tuple>
|
||
#include <utility>
|
||
|
||
|
||
|
||
namespace util {
|
||
|
||
namespace { // recursive builder helper to unpack a sequence...
|
||
|
||
template<size_t N>
|
||
using cnt_ = std::integral_constant<size_t, N>;
|
||
|
||
template<class SEQ>
|
||
inline auto
|
||
_buildSeqTuple (cnt_<0>, SEQ&&)
|
||
{
|
||
return std::tuple<>{};
|
||
}
|
||
|
||
template<size_t N, class SEQ>
|
||
inline auto
|
||
_buildSeqTuple (cnt_<N>, SEQ&& iter)
|
||
{
|
||
auto prefixTuple = std::tie (*iter);
|
||
++iter;
|
||
return std::tuple_cat (prefixTuple, _buildSeqTuple (cnt_<N-1>{}, std::forward<SEQ> (iter)));
|
||
}
|
||
}//(End) unpacking helper
|
||
|
||
|
||
/**
|
||
* Unpack an iterator to build a fixed-size std::tuple of references
|
||
* @tparam N (mandatory) defines the number of elements to unpack; can be zero
|
||
* @param iter anything compliant to the Lumiera Forward Iterator protocol
|
||
* @warning since the implementation uses `std::tie (*iter)`, a _reference_ is
|
||
* stored, which may lead to strange and dangerous behaviour if the given
|
||
* iterator exposes a reference to mutable internal state (e.g. "state core").
|
||
* Moreover, it is assumed the iterator yields enough values to fill the new
|
||
* tuple, and this is not checked; an empty or exhausted iterator might throw,
|
||
* or yield otherwise undefined behaviour.
|
||
*/
|
||
template<size_t N, class SEQ>
|
||
auto
|
||
seqTuple (SEQ&& iter)
|
||
{
|
||
return _buildSeqTuple (cnt_<N>{}, std::forward<SEQ> (iter));
|
||
}
|
||
|
||
|
||
} // namespace util
|
||
#endif /*UTIL_TUPLE_H*/
|