From e6a6fe92d7874aa1d9ee794117e0d7df065c0f1c Mon Sep 17 00:00:00 2001 From: Daniel James Date: Mon, 8 Jul 2013 22:11:54 +0000 Subject: [PATCH] Fix misleading documentation about move support. [SVN r84985] --- doc/compliance.qbk | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/compliance.qbk b/doc/compliance.qbk index f48881ab..771e473d 100644 --- a/doc/compliance.qbk +++ b/doc/compliance.qbk @@ -8,11 +8,12 @@ Support for move semantics is implemented using Boost.Move. If rvalue references are available it will use them, but if not it uses a close, -but imperfect emulation. On such compilers you'll need to use Boost.Move -to take advantage of using movable container elements, also note that: +but imperfect emulation. On such compilers: -* Non-copyable objects can be stored in the containers, but without support - for rvalue references the container will not be movable. +* Non-copyable objects can be stored in the containers. + They can be constructed in place using `emplace`, or if they support + Boost.Move, moved into place. +* The containers themselves are not movable. * Argument forwarding is not perfect. [endsect]