Created on 2009-12-10.00:00:00 last changed 90 months ago
[Moved to DR at the April, 2013 meeting.]
Proposed resolution (February, 2012):
This issue is resolved by the resolution of issue 616.
According to 7.3.2 [conv.lval] paragraph 1, an lvalue-to-rvalue conversion on an uninitialized object produces undefined behavior. Since there is only one “value” of type std::nullptr_t, an lvalue-to-rvalue conversion on a std::nullptr_t glvalue does not need to fetch the value from storage. Is there any need for undefined behavior in this case?
|2014-03-03 00:00:00||admin||set||status: drwp -> cd3|
|2013-10-14 00:00:00||admin||set||status: dr -> drwp|
|2013-05-03 00:00:00||admin||set||messages: + msg4377|
|2013-05-03 00:00:00||admin||set||status: ready -> dr|
|2012-02-27 00:00:00||admin||set||status: review -> ready|
|2011-09-06 00:00:00||admin||set||messages: + msg3500|
|2011-09-06 00:00:00||admin||set||status: open -> review|