std::exception_ptr does not satisfy the requirements of NullablePointer - by Seth__

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 695529 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 10/18/2011 8:33:48 AM
Access Restriction Public


std::exception_ptr does not support some expressions required by NullablePointer. Specifically:

a != b
a != np
np != a

(a and b denote values of a type (possibly const) that satisfies NullablePointer, and np denotes a value of type (possibly const) std::nullptr_t.)
Sign in to post a comment.
Posted by Microsoft on 11/4/2011 at 6:48 PM

Thanks for reporting this bug. We've fixed it, and the fix will be available in VC11.

I carefully compared our exception_ptr implementation to the NullablePointer requirements, and determined that it was also missing boolean testability (e.g. if (p), if (p && stuff)) and swapping. I added them along with the missing op!=() overloads, added a regression test to verify that exception_ptr conforms to NullablePointer's requirements in both syntax and semantics, and additionally improved the performance of comparing exception_ptr to nullptr.

If you have any further questions, feel free to E-mail me at .

Stephan T. Lavavej
Visual C++ Libraries Developer
Posted by MS-Moderator10 [Feedback Moderator] on 10/18/2011 at 8:22 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 10/18/2011 at 8:45 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(