Opened 6 years ago
Last modified 6 years ago
#12810 new Feature Requests
feature parity between boost::intrusive_ptr and boost::interprocess::intrusive_ptr
Reported by: | Owned by: | Ion Gaztañaga | |
---|---|---|---|
Milestone: | To Be Determined | Component: | intrusive |
Version: | Boost Release Branch | Severity: | Not Applicable |
Keywords: | interprocess, intrusive_ptr | Cc: |
Description
Dear all, i'd like to request to bring boost::interprocess::intrusive_ptr interface up to the level of boost::intrusive_ptr, more specifically to add the move operators and e.g. release() method, as discussed on the mailing list (copy below). thanks, Mikolaj
On 13/01/2017 13:42, Mikolaj Krzewicki wrote:
Dear all, would it be possible to add the rvalue operators to interprocess::intrusive_ptr akin to what is already available in "regular" boost::intrusive_ptr:
Move support
#if !defined( BOOST_NO_CXX11_RVALUE_REFERENCES )
intrusive_ptr(intrusive_ptr && rhs) BOOST_NOEXCEPT : px( rhs.px ) {
rhs.px = 0;
}
intrusive_ptr & operator=(intrusive_ptr && rhs) BOOST_NOEXCEPT {
this_type( static_cast< intrusive_ptr && >( rhs ) ).swap(*this); return *this;
}
#endif
Sure, please fill a ticket so this is not forgotten.
Best,
Ion