[LLVMbugs] [Bug 21684] New: Ellipsis at end of generic lambda parameter-declaration-clause should be parsed as a parameter pack

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Thu Nov 27 07:37:52 PST 2014


http://llvm.org/bugs/show_bug.cgi?id=21684

            Bug ID: 21684
           Summary: Ellipsis at end of generic lambda
                    parameter-declaration-clause should be parsed as a
                    parameter pack
           Product: clang
           Version: 3.5
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P
         Component: C++14
          Assignee: unassignedclangbugs at nondot.org
          Reporter: ed at catmur.co.uk
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

void f() { [](auto...){}(); }

prog.cc:1:12: error: no matching function for call to object of type '(lambda
at prog.cc:1:12)'
void f() { [](auto...){}(); }
          ^~~~~~~~~~~~~
prog.cc:1:12: note: candidate function template not viable: requires at least 1
argument, but 0 were provided
1 error generated.

According to [dcl.fct]/14 the ellipsis should be parsed as part of the
abstract-declarator; however gcc parses it as part of the
parameter-declaration-clause.

gcc is similarly incorrect; according to
http://www.reddit.com/r/cpp/comments/2nkcvi/generic_lambda_inconsistency/ MSVC
(latest CTP) is correct.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20141127/0fab13cd/attachment.html>


More information about the llvm-bugs mailing list