LUMIERA.clone/doc/technical/code
Ichthyostega 77c3226948 TreeExplorer: identify yet another subtle type inference problem
surprising behaviour encountered while covering more cases

...obviously the return type of ExpandFunctor::operator()
was inferred as value, even while the invoked functor, from which
this type was deduced, clearly returns a reference.

Solution is simple not to rely on inference, moreover since we know
the exact type in the enclosing scope, thanks to the refactoring which
made this ExpandFunctor a nested class

NOTE:
as it turned out, this is not a compiler bug,
but works as defined by the language:
on return type inference, the detected type is decayed,
which usually helps to prevent returning a reference to a temporary
2017-11-27 05:02:57 +01:00
..
c++11.txt TreeExplorer: identify yet another subtle type inference problem 2017-11-27 05:02:57 +01:00
codingGuidelines.txt LANDING: transition to GTK-3 2015-05-30 17:11:41 +02:00
darkCorners.txt refactoring(#988): switch function-closure to std::tuple 2016-01-19 03:56:53 +01:00
index.txt New documentation section for code base layout and conventions 2011-10-14 03:35:39 +02:00
linkingStructure.txt DOC: summarise suitable mechanisms for dependency decoupling 2015-05-28 03:05:49 +02:00