Home Dashboard Directory Help
Search

*this pointer* fails to bind to rvalue reference to pointer by JesseGood


Status: 

Closed
 as Deferred Help for as Deferred


1
0
Sign in
to vote
Type: Bug
ID: 781977
Opened: 3/23/2013 3:32:05 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Following example fails with `cannot convert from 'A *const ' to 'A *&&'`
struct A
{
void f(){ A*&& a = this; }
};
int main(){}

The this pointer should be a prvalue of type A* in the example according to the C++ standard.
Details
Sign in to post a comment.
Posted by JesseGood on 5/10/2013 at 3:09 PM
Hi Karl,

When I see the same reply "we have decided not to take any action on this feedback at this time" in countless bug reports on Microsoft Connect, it really shows the attitude toward standard C++ conformance. This might be a futile effort, but is there anyway to change policy?
Posted by Microsoft on 4/30/2013 at 5:03 AM
Hi Jesse,

Thank you for taking the time to provide your feedback. After reviewing your reported issue, in the context of all the issues reported to us, we have decided not to take any action on this feedback at this time. We will re-consider our decision for a future release.

If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to http://support.microsoft.com or call 1-800-MICROSOFT for assistance.
For Microsoft premier customers, please contact your administrator, your Technical Account Manager, or your Microsoft premier account representative.

Thanks,
Karl Niu
VC++ Team
Posted by Microsoft on 3/24/2013 at 11:40 PM
Thank you for submitting feedback on Visual Studio 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 Microsoft on 3/23/2013 at 3:52 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)
Sign in to post a workaround.