Re: [Boost-users] [container] Initialization from transformed_range compilation error

Subject: Re: [Boost-users] [container] Initialization from transformed_range compilation error
From: Daniel James (dnljms_at_[hidden])
Date: 2011-09-07 18:07:42

2011/9/7 Ion Gaztañaga <igaztanaga_at_[hidden]>:
> El 07/09/2011 22:30, Daniel James escribió:
>>
>> I noticed that you have a macro BOOST_COPYABLE_AND_MOVABLE_ALT which
>> doesn't define the assignment operator, is that a way to avoid this
>> problem? I'd be tempted to do that, implicit move assignment doesn't
>> seem that important to me.
>
> The problem is that containers already define the non-const assignment
> operator, so there is nothing you can do with this, unless, I put a compile
> time switch to change move emulation in Boost.Container.

Sorry I wasn't clear. I was asking if BOOST_COPYABLE_AND_MOVABLE_ALT
is something I can use in my own code instead of
BOOST_COPYABLE_AND_MOVABLE?