Re: [Boost-bugs] [Boost C++ Libraries] #8092: stdlibc++ shipped by Apple does not provide std::move

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8092: stdlibc++ shipped by Apple does not provide std::move
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-03-04 08:40:03

#8092: stdlibc++ shipped by Apple does not provide std::move
-------------------------------+--------------------------------------------
  Reporter:  anonymous         |       Owner:  johnmaddock    
      Type:  Bugs              |      Status:  new            
 Milestone:  To Be Determined  |   Component:  config         
   Version:  Boost 1.53.0      |    Severity:  Showstopper    
Resolution:                    |    Keywords:  xcode,osx,clang
-------------------------------+--------------------------------------------

Comment (by michel):

 Detecting the clang and libstdc++-4.2 configuration is not so difficult.
 (I needed to detect it in `boost/type_traits/intrinsics.hpp` to avoid
 the problems about `__is_pod`/`__is_empty`.)
 But I don't want to disable rvalue refs, since the compiler does
 support the feature.

 Another solutions would be to use workaround implementations, but
 * We cannot add workaround implementations of `std::move/forward`
   as `boost::move/forward`, since the name `boost::move/forward` is
   already used by the Boost.Move library.
 * We cannot use `boost::forward` in Boost.Move as a drop-in replacement of
   `std::forward`, since `boost::forward` is not equivalent to
 `std::forward`.
   We cannot use `static_cast<T&&>` either, due to the same reason.

 I don't think it's worth the effort to support this configuration.
 I would say "Don't turn on -std=c++0x option in this configuration
 or use another stdlib that supports C++11."

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