$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] [result_of] Make `cpp0x_result_of_impl` public
From: Stephan T. Lavavej (stl_at_[hidden])
Date: 2012-03-28 00:02:34
[STL]
> 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.)
[Eric Niebler]
> 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!>
Occasionally, users (correctly) complain that VC10's result_of doesn't work with lambdas (which don't provide result_type). Users who keep using VC10, for whatever reason, after VC11 is released may want a decltype-powered alternative. However, this usually comes up when they're trying to bind() a lambda, which isn't an especially compelling scenario. It's better to write a lambda that effectively binds arguments itself. (In fact, I would have preferred to deprecate bind() in C++11.) Some users writing highly generic code may have a stronger need for a decltype-powered result_of - but these are precisely the kind of users that would be affected by decltype v1.0.
STL