public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andrew.n.sutton at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66834] [concepts] concept parameter kind mismatch causes hard error
Date: Sat, 11 Jul 2015 15:32:00 -0000	[thread overview]
Message-ID: <bug-66834-4-uekRl5LQFq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66834-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Sutton <andrew.n.sutton at gmail dot com> ---
I think that this is invalid too. There's an expansion from an
uninstantiated template argument pack into a pair of template
parameters.

I think the program must be ill-formed in this case. It's not possible
to substitute a single pack through the two parameters declared for
ExplicitlyConvertible in order to normalize the constraint.

The TS is silent on this, but the resolution should be the same as that of
1430.

Andrew Sutton


On Fri, Jul 10, 2015 at 10:48 PM, jason at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66834
>
> --- Comment #1 from Jason Merrill <jason at gcc dot gnu.org> ---
> This was introduced by my patch for bug 66092, applying the tentative
> resolution of core issue 1430 to concepts as well as alias templates.  This
> makes sense to me since they have the same issue of needing to substitute
> dependent arguments into the template, in this case during normalization.
>
> So I think your example is invalid, but it could use some discussion in core.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.


  parent reply	other threads:[~2015-07-11 15:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 17:56 [Bug c++/66834] New: " eric.niebler at gmail dot com
2015-07-11  2:48 ` [Bug c++/66834] " jason at gcc dot gnu.org
2015-07-11 15:32 ` andrew.n.sutton at gmail dot com [this message]
2015-07-11 17:29 ` eric.niebler at gmail dot com
2015-07-11 17:53 ` eric.niebler at gmail dot com
2015-07-11 19:09 ` eric.niebler at gmail dot com
2015-07-13 20:16 ` jason at gcc dot gnu.org
2015-07-13 20:31 ` jason at gcc dot gnu.org
2015-07-14  4:10 ` jason at gcc dot gnu.org
2015-07-14  4:11 ` jason at gcc dot gnu.org
2015-07-14 13:33 ` andrew.n.sutton at gmail dot com
2015-07-14 14:47 ` jason at gcc dot gnu.org
2015-07-17 17:43 ` jason at gcc dot gnu.org
2015-08-04 13:37 ` jason at gcc dot gnu.org
2020-10-15 18:54 ` [Bug c++/66834] [concepts] variadic concepts and DR 1430 ppalka at gcc dot gnu.org

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-66834-4-uekRl5LQFq@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).