Opened 10 years ago
Closed 4 years ago
#7601 closed Bugs (obsolete)
Does not use Boost.Move
| Reported by: | Dave Abrahams | Owned by: | ebf |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | variant |
| Version: | Boost 1.52.0 | Severity: | Problem |
| Keywords: | Cc: | antoshkka@… |
Description (last modified by )
Variant contains its own move semantics emulation, which is apparently undocumented and untested (although people seem to think it's something it isn't—see http://j.mp/SpAyRZ). That should be replaced by the use of Boost.Move so the wishful thinking becomes reality.
Change History (5)
comment:1 by , 10 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 9 years ago
comment:3 by , 9 years ago
(In [85408]) Merge from trunk:
- Fix issue with const rvalue references in Boost.Variant (fixes #8988)
- Get rid of Boost.Variant hand written non-usable move emulation and use Boost.Move instead(refs #7601). This does not mean that Boost.Variant supports move emulation now, but removes duplicate/non-working code and makes sure that Boost.Variant is able to work with boost::move
comment:4 by , 9 years ago
| Cc: | added |
|---|
comment:5 by , 4 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Supporting rvalue reference emulation in 2018 does not seem to be a highly requested feature.
Note:
See TracTickets
for help on using tickets.
(In [85159]) Get rid of Boost.Variant hand written non-usable move emulation and use Boost.Move instead (refs #7601). This commit does not make Boost.Variant use move emulated assignments in all situations, but at least removes duplicate/non-working code and makes sure that Boost.Variant is able to work with boost::move (one step closer to full support of rvalue references emulations).