On 20/12/18 22:53 +0100, François Dumont wrote:
On 12/20/18 9:04 AM, Ville Voutilainen wrote:
On Thu, 20 Dec 2018 at 08:29, François Dumont wrote:
Hi
I eventually find out what was the problem with the
std::move_if_noexcept within associative containers.
The std::pair move default
On Thu, 20 Dec 2018 at 23:53, François Dumont wrote:
> >> This is why I am partially specializing __move_if_noexcept_cond. As
> >> there doesn't seem to exist any Standard meta function to find out if
> >> move will take place I resort using std::is_const as in this case for
> >> sure the co
On 12/20/18 9:04 AM, Ville Voutilainen wrote:
On Thu, 20 Dec 2018 at 08:29, François Dumont wrote:
Hi
I eventually find out what was the problem with the
std::move_if_noexcept within associative containers.
The std::pair move default constructor might not move both first
and secon
On Thu, 20 Dec 2018 at 08:29, François Dumont wrote:
>
> Hi
>
> I eventually find out what was the problem with the
> std::move_if_noexcept within associative containers.
>
> The std::pair move default constructor might not move both first
> and second member. If any is not moveable it w
