Re: [boost] [result_of, phoenix] Inconsistency between result_of and tr1_result_of

Subject: Re: [boost] [result_of, phoenix] Inconsistency between result_of and tr1_result_of
From: Michel Morin (mimomorin_at_[hidden])
Date: 2012-05-17 11:13:34

Eric Niebler wrote:
>> Shouldn't we provide specializations for both `result_of` and
>> `tr1_result_of` to make result_of and tr1_result_of equivalent?
>
> Yes. Can you file bug reports?
>
>> (Additional question: Should we avoid the specialization of result_of
>> when we use decltype-based result_of?)
>
> Probably. More bug reports, please! :-)

Done.

[Add tr1_result_of specialization and avoid
specialization of decltype-based result_of]
* Functional/Forward
  https://svn.boost.org/trac/boost/ticket/6909
* Fusion
  https://svn.boost.org/trac/boost/ticket/6910
* Phoenix V3
  https://svn.boost.org/trac/boost/ticket/6911
* Phoenix V2
  https://svn.boost.org/trac/boost/ticket/6912

[Avoid specialization of decltype-based result_of]
* Proto
  https://svn.boost.org/trac/boost/ticket/6913

[Feature request: Add result_of and tr1_result_of
specializations for nullary function calls]
* Lambda
  https://svn.boost.org/trac/boost/ticket/6914

Regards,
Michel