
10 Aug
2011
10 Aug
'11
4:54 a.m.
El 09/08/2011 20:23, Antony Polukhin escribió:
2011/8/8 Stephan T. Lavavej<stl@exchange.microsoft.com>:
[Antony Polukhin]
The problem is that VC10 uses move() in it's STL implementation without directly specifying namespace. That leads to ambiguity, when VC10 containers are used with boost classes.
I can't retroactively fix VC10, but at least I can fix the next major version.)
It means that a workaround for VC10 is still required. Can we just make
namespace boost { using std::move; }
I guess we should do the same for std::forward. Is VC10 move/move strictly standard conforming? This needs some tweaks in Move (what about std::move(Input, InputIt, OutIt)?). MSVC defines also move_backward but not uninitialized_move, etc. Best, Ion