Re: [Boost-bugs] [Boost C++ Libraries] #6913: [Proto] Avoid specialization of decltype-based result_of

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #6913: [Proto] Avoid specialization of decltype-based result_of
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-05-21 06:51:31

#6913: [Proto] Avoid specialization of decltype-based result_of
--------------------------------------+-------------------------------------
  Reporter:  michel                   |       Owner:  eric_niebler
      Type:  Bugs                     |      Status:  closed      
 Milestone:  To Be Determined         |   Component:  proto       
   Version:  Boost Development Trunk  |    Severity:  Problem     
Resolution:  wontfix                  |    Keywords:              
--------------------------------------+-------------------------------------
Changes (by eric_niebler):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 I know I asked you to file this bug. But when I went to make the change, I
 found I had left myself the following comment in the code:

 {{{
 // Specializations of boost::result_of and boost::tr1_result_of to
 eliminate
 // some unnecessary template instantiations
 }}}

 The comment is correct. Although strictly unnecessary in a decltype world,
 the {{{boost::result_of}}} specializations do bring down the number of
 template instantiations, which speeds up compile times. The
 specializations aren't actually hurting anything, so I'm leaving them in.
 (Note also the specializations are for unary function invocations, so they
 were never there to address the nullary limitation of
 {{{tr1::result_of}}}. They are strictly to bring down TMP overhead.)

 If you find a situation where the specializations are causing a problem,
 feel free to reopen this bug. Thanks.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/6913#comment:1>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.