lumiera_/src
Ichthyostega ce7c38312d iterator improvements: use Lumiera Forward Iterator in range for loops
This is kind of the logic consequence, since we consider our
functional iterator concept still superior and will continue
to rely on it.

For some time now, I've considered to build a generic bridge
function, to use enable_if and metaprogramming to figure out
if some type is a "Lumiera Forward Iterator" automatically.
But since our concept is to some degree a contract regarding
semantics, which never can be captured by any kind of introspection,
such a bridge implementation would be rather heuristic and
bears the danger to trigger on types actually not intended
as iterator at all. So I consider such a solution as dangerous
and we'll settle with just supplying the necessary bridge
functions as free functions injected for ADL on a case by case base
2015-08-16 01:35:28 +02:00
..
backend clean-up: sourcefile layout and spell checking 2014-10-23 23:04:35 +02:00
common Ticket #155: rename Track -> Fork (II) 2015-05-31 02:03:24 +02:00
gui LANDING: transition to GTK-3 2015-05-30 17:11:41 +02:00
include Ticket #155: rename Track -> Fork (II) 2015-05-31 02:03:24 +02:00
lib iterator improvements: use Lumiera Forward Iterator in range for loops 2015-08-16 01:35:28 +02:00
lumiera release prep: remove defunct autotools buildsystem 2013-10-29 03:47:50 +01:00
plugin Merge: change building to create modules 2008-12-20 02:15:33 +01:00
proc Ticket #155: rename Track -> Fork (II) 2015-05-31 02:03:24 +02:00
tool clean-up: sourcefile layout and spell checking 2014-10-23 23:04:35 +02:00
.gitignore
DIR_INFO update some DIR_INFO entries 2011-04-05 00:44:30 +02:00
doxygen.dox DOC: reorganise the Doxygen configuration and structure 2013-10-25 06:34:38 +02:00
SConscript enable special unit-tests to link against the gui 2014-10-18 04:27:07 +02:00