public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102928] Template argument deduction when mixing variadic template with C-style variadic function
Date: Sat, 06 Nov 2021 22:10:56 +0000	[thread overview]
Message-ID: <bug-102928-4-KkF3LXT285@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102928-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102928

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-11-06
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
temp.deduct.call

For a function parameter pack that occurs at the end of the
parameter-declaration-list,
deduction is performed for each remaining argument of the call, taking the type
P of the declarator-id of the
function parameter pack as the corresponding function template parameter type.
Each deduction deduces
template arguments for subsequent positions in the template parameter packs
expanded by the function
parameter pack.


parameter-declaration-list does not include the ... variadic arguments part.

So Confirmed.

As far as I read in the standard, the template variadic deduction should be
greedy (deduction is performed for each remaining argument of the call).

      reply	other threads:[~2021-11-06 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 12:29 [Bug c++/102928] New: " cerrigno at gmail dot com
2021-11-06 22:10 ` pinskia at gcc dot gnu.org [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-102928-4-KkF3LXT285@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).