non-class rvalues always have cv-unqualified types

by

The committee already seems to be aware that there’s a problem in this part of the standard. CWG issue 690 talks about a somewhat similar problem with exactly the same part of the standard (in the “additional note” from September, 2009). I’d guess new language will be drafted for that part of the standard soon.

Edit: I’ve just submitted a post on comp.std.c++, noting the problem and suggesting new wording for the relevant piece of the standard. Unfortunately, being a moderated newsgroup, nearly everybody will probably have forgotten this question by the time it makes it through the approval queue there.

More Related Contents:

  1. Rvalue Reference is Treated as an Lvalue?
  2. In C++, what categories (lvalue, rvalue, xvalue, etc.) can expressions that produce temporaries of class type fall into?
  3. On how to recognize Rvalue or Lvalue reference and if-it-has-a-name rule
  4. Passing rvalues through std::bind
  5. Rule-of-Three becomes Rule-of-Five with C++11? [closed]
  6. What are the main purposes of using std::forward and which problems it solves?
  7. What does T&& (double ampersand) mean in C++11?
  8. Move capture in lambda
  9. Do rvalue references to const have any use?
  10. Why is `std::move` named `std::move`?
  11. Syntax for universal references
  12. Why are rvalues references variables not rvalue?
  13. Is the pass-by-value-and-then-move construct a bad idiom?
  14. Why user-defined move-constructor disables the implicit copy-constructor?
  15. What’s a use case for overloading member functions on reference qualifiers?
  16. Is it possible to std::move objects out of functions? (C++11)
  17. Why do some people use swap for move assignments?
  18. Do rvalue references allow dangling references?
  19. Can I typically/always use std::forward instead of std::move?
  20. Can compiler generate std::move for a last use of lvalue automatically?
  21. What are the main purposes of std::forward and which problems does it solve?
  22. Isn’t the const modifier here unnecessary? [duplicate]
  23. C++11 rvalue reference calling copy constructor too
  24. Is it valid to bind non-const lvalue-references to rvalues in C++ 11?(modified)
  25. Understanding rvalue references
  26. Operator overload which permits capturing with rvalue but not assigning to
  27. How to determine programmatically if an expression is rvalue or lvalue in C++?
  28. Why does std::forward have two overloads?
  29. Overloading on R-value references and code duplication
  30. Is there a reference_wrapper for rvalue references?

Leave a Comment