Boost C++ Libraries: Ticket #1841: Optional: C++0x features

mlcreech@… — Fri, 04 Feb 2011 20:54:46 GMT

Are there any plans to add support for rvalue references to boost::optional? This makes a very big difference on C++0x code.

Also, bug severity should not be "optimization" - as things are, classes which are movable but not copyable can't be used at all with boost::optional (compile errors), whereas if move semantics were respected it would work fine.

attachment set

mlcreech@… — Fri, 04 Feb 2011 22:17:59 GMT

attachment → 14-optional-partial-rvalue.patch

Partial move support

mlcreech@… — Fri, 04 Feb 2011 22:19:25 GMT

I've attached an example patch which fixes my build problems when using boost::optional with noncopyable objects. It doesn't handle move semantics for boost::optional objects themselves, but does for the underlying type.

NN — Wed, 09 Feb 2011 12:40:00 GMT

I support this patch. C++0x move feature makes code much better optimized !

Fernando Cacciola — Thu, 17 Feb 2011 13:26:39 GMT

I will be working on adding this next week or the one after.

Best

boost@… — Mon, 05 Dec 2011 07:33:46 GMT

Hi, I stumbled across this ticket while looking for a solution for the same issues with move-only types in Boost.Optional, will there be a fix anytime near in the future?

Regards, Arne

version, type, severity changed

mlcreech@… — Mon, 05 Dec 2011 13:06:22 GMT

version Boost 1.35.0 → Boost 1.38.0
type Feature Requests → Patches
severity Optimization → Problem

Arne, does this patch work for you? It at least fixed the build problems I was having. I'm still using it with 1.48, I'll post an updated version.

I'm going to change the type/severity also: this problem prevents code from building which should otherwise work when move semantics are enabled.

attachment set

mlcreech@… — Mon, 05 Dec 2011 13:07:06 GMT

attachment → 14-optional-partial-rvalue.2.patch

Updated patch for 1.48

status changed

Fernando Cacciola — Fri, 13 Jan 2012 02:42:05 GMT

status new → assigned

I started work on this

version changed

jmckesson@… — Mon, 09 Jul 2012 04:38:25 GMT

version Boost 1.38.0 → Boost 1.50.0

Is this going to be implemented anytime soon?

tjackson@… — Thu, 11 Oct 2012 19:14:05 GMT

I'd love to see this completed. Any updates?

zeratul976@… — Sun, 21 Oct 2012 07:52:45 GMT

+1, I'd like to see this as well!

Fernando Cacciola — Mon, 22 Oct 2012 13:03:08 GMT

I (re)-started working on it this week.

Mozza314 — Thu, 21 Mar 2013 01:10:40 GMT

+1 Surely this is a no-brainer. optional should take advantage of move semantics.

Lindley — Thu, 24 Oct 2013 18:33:35 GMT

This still appears to be unfixed in 1.54. This needs to get done.

As it stands now, this bug prevents the Signals2 library from being used with a move-only return value from a slot such as a std::future, among other things.

owner, status, version, milestone changed

akrzemi1 — Fri, 06 Jun 2014 11:30:56 GMT

owner changed from Fernando Cacciola to akrzemi1
status assigned → new
version Boost 1.50.0 → Boost 1.56.0
milestone Boost 1.36.0 → Boost 1.56.0

status, version changed; resolution set

akrzemi1 — Fri, 06 Jun 2014 11:32:26 GMT

status new → closed
version Boost 1.56.0 → Boost 1.36.0
resolution → fixed

move semantics, improved swap and function emplace() added in branch master.