22 Apr
2011
22 Apr
'11
11:28 a.m.
Eric Niebler wrote:
On 4/22/2011 4:18 PM, Ivan Le Lann wrote:
In C++11, I think this could be fixed with rvalue refs detection. Shouldn't any function relying on the fact that its arguments still exist after the call do that check?
So either delete the &&-function or ... [disclaimer: ugly but funny] make it move the range inside the adaptor somehow.
Agreed. If this is fixed at all, it should be fixed in Boost.Range, and moving an rvalue container into the range adapter makes perfect sense to me.
Yeah, that's a fundamental solution. Regards, Michel