How to make template rvalue reference parameter ONLY bind to rvalue reference?

by

You can restrict T to not be an lvalue reference, and thus prevent lvalues from binding to it:

#include <type_traits>

struct OwnershipReceiver
{
  template <typename T,
            class = typename std::enable_if
            <
                !std::is_lvalue_reference<T>::value
            >::type
           >
  void receive_ownership(T&& t)
  {
     // taking file descriptor of t, and clear t
  }
};

It might also be a good idea to add some sort of restriction to T such that it only accepts file descriptor wrappers.

More Related Contents:

  1. Rule-of-Three becomes Rule-of-Five with C++11? [closed]
  2. What are the main purposes of using std::forward and which problems it solves?
  3. What does T&& (double ampersand) mean in C++11?
  4. C++11 rvalues and move semantics confusion (return statement)
  5. Rvalue Reference is Treated as an Lvalue?
  6. Is returning by rvalue reference more efficient?
  7. Move capture in lambda
  8. C++11 make_pair with specified template parameters doesn’t compile
  9. Do rvalue references to const have any use?
  10. Why is `std::move` named `std::move`?
  11. Overload resolution between object, rvalue reference, const reference
  12. How to actually implement the rule of five?
  13. Why user-defined move-constructor disables the implicit copy-constructor?
  14. What’s a use case for overloading member functions on reference qualifiers?
  15. In C++, what categories (lvalue, rvalue, xvalue, etc.) can expressions that produce temporaries of class type fall into?
  16. Is it possible to std::move objects out of functions? (C++11)
  17. Can compiler generate std::move for a last use of lvalue automatically?
  18. On how to recognize Rvalue or Lvalue reference and if-it-has-a-name rule
  19. What are the main purposes of std::forward and which problems does it solve?
  20. Is there any case where a return of a RValue Reference (&&) is useful?
  21. Passing rvalues through std::bind
  22. Should a move constructor take a const or non-const rvalue reference?
  23. C++11 rvalue reference calling copy constructor too
  24. Understanding rvalue references
  25. Operator overload which permits capturing with rvalue but not assigning to
  26. problems with Move constructor and Move overloaded assignment operator?
  27. Overloading on R-value references and code duplication
  28. How does std::forward receive the correct argument?
  29. Is there a reference_wrapper for rvalue references?
  30. C++ forwarding reference and r-value reference

Leave a Comment