Re: [boost] [result_of] Make `cpp0x_result_of_impl` public

Subject: Re: [boost] [result_of] Make `cpp0x_result_of_impl` public
From: Eric Niebler (eric_at_[hidden])
Date: 2012-03-27 23:45:15

On 3/27/2012 6:38 PM, Stephan T. Lavavej wrote:
> [Michel Morin]
>>> Boost's users who (b) have compilers that support decltype and (c) don't
>>> support N3256 and (d) don't have a std::result_of that uses decltype.
>>> I'm pretty sure that's exactly zero people.
>> 
>> Right! Forgot about std::result_of.
>> 
>> (Though gcc-4.4 supports decltype and does not provide decltype-based
>> std::result_of, gcc-4.4 is old and no longer maintained release series.)
> 
> Sorry, I haven't been following this thread, but VC10 has decltype v1.0 (not v1.1) and its std::result_of follows the TR1 protocol (not decltype-powered). Is that of interest?
> 
> (VC11 has decltype v1.1 and its std::result_of is decltype-powered.)

Thanks, Stephan. That makes the picture murkier. So do we add
cxx11_result_of, support it, doc it and test it indefinitely, for the
sake of the users of one version of one compiler? <sigh!>

I, for one, would rather spend my energy elsewhere. Like making
boost::result_of use decltype by default on compliant compilers. Which I
hope to do on trunk in the very near future.

Any objections to this plan?

-- 
Eric Niebler
BoostPro Computing
http://www.boostpro.com