
30 Nov
2010
30 Nov
'10
10:40 a.m.
Dave Steffen wrote:
Hi
Coming back to this issue after a week or two... trying the above
[changing to std::forward]
made no difference: no compiler warnings, and no change in Valgrind's error messages.
Looks like a g++ bug then. You should try reproducing it in a self-contained example and report it to the GCC Bugzilla. I'm not sure what we can do on our end to avoid it. (I'll switch to std::forward in any case, since this seems a good idea in general, but it won't help in this specific case.)