feedc0de/boost_unordered
1
0
Fork 0
forked from boostorg/unordered
Code Pull Requests Activity

Fix misleading documentation about move support.

Browse Source 
[SVN r84985]
This commit is contained in:
Daniel James
2013-07-08 22:11:54 +00:00
parent fb93c8cb86
commit e6a6fe92d7
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/compliance.qbk
View File

@ -8,11 +8,12 @@
Support for move semantics is implemented using Boost.Move. If rvalue 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, 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 but imperfect emulation. On such compilers:
to take advantage of using movable container elements, also note that:
* Non-copyable objects can be stored in the containers, but without support * Non-copyable objects can be stored in the containers.
for rvalue references the container will not be movable. 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. * Argument forwarding is not perfect.
[endsect] [endsect]