Opened 12 years ago
Closed 10 years ago
#4711 closed Bugs (fixed)
Must use implementation details to return move-only types
Reported by: | Dave Abrahams | Owned by: | viboes |
---|---|---|---|
Milestone: | Boost 1.50.0 | Component: | thread |
Version: | Boost 1.44.0 | Severity: | Problem |
Keywords: | move | Cc: | viboes |
Description
I can't directly return a move-only type and must instead return boost::detail::thread_move_t<…>
. That should be improved/fixed. It is possible to write move emulation that allows them to be returned directly.
Change History (9)
comment:1 by , 12 years ago
Type: | Bugs → Support Requests |
---|
comment:2 by , 12 years ago
Take any move-only type from the library and try to return it from a function, using only documented APIs. For me it fails unless I use something from namespace detail
. It's been a while, so I don't have the code handy, but is this clear enough?
follow-up: 4 comment:3 by , 12 years ago
Cc: | added |
---|
Please could you provide a short test? This is a way to help the Boost community.
comment:4 by , 12 years ago
Replying to viboes:
Please could you provide a short test? This is a way to help the Boost community.
Not that I often pass up an opportunity to help the Boost community, but I don't think I'll have time to build one anytime soon. That said, you have all the info here that you should need to write one yourself.
comment:5 by , 11 years ago
Type: | Support Requests → Bugs |
---|
comment:6 by , 11 years ago
Keywords: | move added |
---|
There is an action point to use Boost.Move. Could we consider this as a duplicate of #6194 Adapt to Boost.Move.
comment:7 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:8 by , 11 years ago
Milestone: | To Be Determined → Boost 1.49.0 |
---|
comment:9 by , 10 years ago
Milestone: | Boost 1.49.0 → Boost 1.50.0 |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Documentation has been added for the new Boost.Move move semantics and the old one.
Committed in release branch at [78543]
I have moved it to support until the issue is clarified. Please could you be more explicit?