You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
crash with a SIGSEGV. Apparently all getters which internally return a const reference are affected. Observed with gcc 5.4.0. Unclear whether this is a coding bug introduced when boost::bind was replaced by lambdas (in commit 1620ee3) or a compiler issue.
The text was updated successfully, but these errors were encountered:
- automatic return type detection for lambda's can be error prone
- it is safer and more compact to use std:bind as method forwarder
- closes issue #19
The culprit was that automatic return type determination for the getter lambdas was used. This fails when the called method returns a reference of an object. The deduced lambda return type will the object, not a reference. Unfortunately this doesn't lead to a compile time error but to a run time error.
Bottom lime is
automatic return type detection for lambda's can be error prone
it is safer and also more compact to use std:bind as method forwarder
tcl commands like
crash with a
SIGSEGV
. Apparently all getters which internally return aconst
reference are affected. Observed withgcc 5.4.0
. Unclear whether this is a coding bug introduced whenboost::bind
was replaced by lambdas (in commit 1620ee3) or a compiler issue.The text was updated successfully, but these errors were encountered: