Visual Studio and .NET Framework Home
Thank you for your feedback!
is_pod<void>::value returns true (1)
- by JamesWebb
This item has been fixed in the current or upcoming version of this product.
A more detailed explanation for the resolution of this particular item may have been provided in the comments section.
3/24/2012 12:51:32 PM
Sent to Engineering Team for consideration
To my knowledge 'is_pod<void>::value' should return false (0)
ATTACH A FILE
EDIT THIS ITEM
Item can only be reassigned when it is active.
to post a comment.
Please enter a comment.
on 9/26/2012 at 2:33 PM
Thanks for reporting the bug. We've fixed it, and the fix will be available in the next release of our C++ Standard Library implementation.
Note: Connect doesn’t notify me about comments; if you have further questions, please e-mail me.
Visual C++ Libraries
on 6/18/2012 at 3:54 PM
Thanks for reporting this bug. I'm Microsoft's maintainer of the STL, and I wanted to let you know that while this bug remains active in our database, it won't be fixed in VC11 RTM (VS 2012 RTM). All bugs are important to us, but some are more severe than others and rise to the top of our priority queue.
I'm copying-and-pasting this response across all of the STL's active Connect bugs, but the following terse comments apply specifically to your bug:
* I agree that is_pod<void> should be false. We'll need to audit the other type traits for their answers with void (as a "special" type, it's a source of bugs).
I can't promise when we'll be able to resolve this bug, but we hope to do so as soon as possible (and I'll send another response when that happens) - our first opportunity will be the "out of band" release between VC11 and VC12 that Herb Sutter announced at the GoingNative 2012 conference.
Note: Connect doesn't notify me about comments. If you have any further questions, please E-mail me.
Stephan T. Lavavej
Senior Developer - Visual C++ Libraries
[Feedback Moderator] on 3/25/2012 at 7:18 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 review. We will contact you if we require any additional information.
on 3/24/2012 at 1:47 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
to post a workaround.
Please enter a workaround.
Attach a file
© 2015 Microsoft