This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 115a. See for the official list.


1013. Uninitialized std::nullptr_t objects

Section: 7.3.2  [conv.lval]     Status: CD3     Submitter: Miller     Date: 2009-12-10

[Moved to DR at the April, 2013 meeting.]

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?

Proposed resolution (February, 2012):

This issue is resolved by the resolution of issue 616.