Re: [boost] [smart_ptr] error with nullptr_t

Subject: Re: [boost] [smart_ptr] error with nullptr_t
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2012-12-19 01:14:09

On Wed, Dec 19, 2012 at 8:47 AM, Eric Niebler <eric_at_[hidden]> wrote:
> On 12/11/2012 6:31 PM, Peter Dimov wrote:
>> John Bytheway wrote:
>>> I believe std::nullptr_t could be replaced with decltype(nullptr), which
>>> would allow this support to be offered without standard library
>>> assistance.
>>
>> Your belief is correct, but I deliberately didn't mention this option
>> for aesthetic reasons. :-)
>>
>> If we're going to support this configuration, I think that the sensible
>> thing to do would be for Boost.Config to define std::nullptr_t,
>> std::move, std::forward, and whatever else is missing and necessary.
>> However... I'm not sure that Boost.Config would be able to detect it.
>
> I just got bit by this. For the record, I don't think it's
> Boost.Config's business to be defining std::move, std::forward, etc.

+1, we already have Boost.Move for this.