On Thu, Apr 8, 2010 at 2:44 PM, Daniel James <dnljms@gmail.com> wrote:
On 8 April 2010 19:18, Eric Niebler <eric@boostpro.com> wrote:
Now, I'd like to re-raise the issue of commenting out for now the decltype-based implementation of result_of both on trunk and release. This is time-critical and a blocker for proto, xpressive and spirit on msvc-10, gcc in c++0x mode, and any other compiler that implements decltype. Let's do it on trunk, see what breaks (nothing, I hope) and try to get it in 1.43. We can always revert later.
The decltype implementation was only recently merged to release, we can just revert the merge.
I suppose it's fine to revert the merge. Some compilers are already shipping with a std::result_of that implements the current draft standard. So boost::result_of isn't so critical for these users. Daniel Walker