Opened 14 years ago
Closed 12 years ago
#2738 closed Feature Requests (wontfix)
at_thread_exit move overloading
| Reported by: | viboes | Owned by: | Anthony Williams | 
|---|---|---|---|
| Milestone: | Boost 1.39.0 | Component: | thread | 
| Version: | Boost 1.37.0 | Severity: | Optimization | 
| Keywords: | at_thread_exit move | Cc: | 
Description
What do you think about adding move support for at_thread_exit?
template<typename F> void at_thread_exit(F&& f);
and be emulated with the following prototypes?
template<typename F> void at_thread_exit(detail::thread_move_t<F> f); template<typename F> void at_thread_exit(F f, typename disable_if<boost::is_convertible<F&,detail::thread_move_t<F> >, dummy* >::type=0);
BTW, could you tell us why this function is not included on the C++0x proposal?
  Note:
 See   TracTickets
 for help on using tickets.
    

This modification forces the function F to follow the specific Boost.Thread move semantics, which I don't think it is desirable.
I think it will be better to wait until Boost.Thread replace its own move semantics by the one provided by Boost.Move (of course if accepted).