6 May
2016
6 May
'16
6:38 a.m.
On 06/05/2016 00:13, Stephan T. Lavavej wrote:
[Vladimir Prus]
Thanks - that sounds like unfortunate situation, and that boost::any can't do much, as its constructor is designed to accept anything.
Can you avoid using 1-tuples internally? 2-tuples aren't affected by this breaking change.
Are you suggesting that boost::signals2 specially handles the case of 1 parameter, and starts using 2-tuples in that case? Only Frank can tell how much effort that would be, but it sounds rather intrusive. -- Vladimir Prus http://vladimirprus.com