Search

empty parameter pack not remembered when calling member ctor by Bengt Gustafsson

Closed
as Fixed Help for as Fixed

1
0
Sign in
to vote
Type: Bug
ID: 780151
Opened: 2/27/2013 1:40:04 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
In the Tuple ctor the tail can't be initialized according to the error message, which says that two parameters are sent, but as the parameter pack is empty there should be only one parameter in the call to the mTail ctor, the D2.

NOTE: By uncommenting line 1 a functioning version is enabled. But I'm not sure that this is valid C++11 even though it compiles. Both specializations should be eligible for the 1 parameter case. However, the compiler seems to prefer the one without a parameter pack. I don't know if this is according to the standard, I could not find any text about it. Can it be relied on to work on any compliant compiler?
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Compile attached file.

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

1>c:\ru\minituple.cpp(17): error C2661: 'Tuple<D2>::Tuple' : no overloaded function takes 2 arguments

Expected results


functioning code
File Attachments
File Name Submitted By Submitted On File Size  
minituple.cpp 2/27/2013 1 KB
Sign in to post a comment.
Posted by Microsoft on 3/11/2013 at 11:34 AM
Hi: this bug has been fixed. The fix will show up in the next release of Visual C++

Thanks
Jonathan Caves
Visual C++ Compiler Team
Posted by Microsoft on 2/27/2013 at 6:03 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/27/2013 at 1:50 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.