Created on 2011-03-21.00:00:00 last changed 90 months ago
[Moved to DR at the October, 2012 meeting.]
Additional note, January, 2012:
An objection has been raised to the proposed resolution on the basis that it unnecessarily weakens the distinction between rvalues and lvalues, making it easier to create dangling references. Its status has therefore been changed back to "review" to allow further discussion.
Proposed resolution (August, 2011):
Change 184.108.40.206 [expr.dynamic.cast] paragraph 6 as follows:
Otherwise, v shall be a pointer to or
an lvalueof a polymorphic type (11.7.3 [class.virtual]).
220.127.116.11 [expr.dynamic.cast] paragraph 2 allows an expression of any value category when the target type is an rvalue reference. However, paragraph 6 requires that the operand be an lvalue if the runtime check is to be applied. This requirement should presumably be relaxed to require only a glvalue when the target type is an rvalue reference.
|2014-03-03 00:00:00||admin||set||status: drwp -> cd3|
|2013-05-03 00:00:00||admin||set||status: dr -> drwp|
|2012-11-03 00:00:00||admin||set||messages: + msg4128|
|2012-11-03 00:00:00||admin||set||status: ready -> dr|
|2012-02-27 00:00:00||admin||set||status: review -> ready|
|2012-01-17 00:00:00||admin||set||messages: + msg3599|
|2012-01-17 00:00:00||admin||set||status: ready -> review|
|2011-09-06 00:00:00||admin||set||messages: + msg3432|