public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111485] New: Constraint mismatch on template template parameter
Date: Tue, 19 Sep 2023 16:50:52 +0000 [thread overview]
Message-ID: <bug-111485-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111485
Bug ID: 111485
Summary: Constraint mismatch on template template parameter
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: barry.revzin at gmail dot com
Target Milestone: ---
Reduced from StackOverflow (https://stackoverflow.com/q/77136297/2069064):
template <typename T> constexpr bool regular = true;
template <typename T> concept C = regular<T>;
template<template<C> typename T> struct example { };
template<template<C> typename T> using example_t = example<T>;
gcc 13.2 rejects with:
<source>:6:61: error: constraint mismatch at argument 1 in template parameter
list for 'template<template<class> class requires C< <template-parameter-2-1>
> T> struct example'
6 | template<template<C> typename T> using example_t = example<T>;
| ^
<source>:6:61: note: expected 'template<class> class requires C<
<template-parameter-2-1> > T' but got 'template<class> class requires C<
<template-parameter-2-1> > T'
But this should be fine. Clang and MSVC accept. "
next reply other threads:[~2023-09-19 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 16:50 barry.revzin at gmail dot com [this message]
2023-09-19 17:29 ` [Bug c++/111485] [11/12/13/14 Regression] " ppalka at gcc dot gnu.org
2023-09-22 10:26 ` cvs-commit at gcc dot gnu.org
2023-09-24 18:42 ` cvs-commit at gcc dot gnu.org
2023-12-24 15:11 ` [Bug c++/111485] [11/12 " cvs-commit at gcc dot gnu.org
2023-12-24 15:12 ` cvs-commit at gcc dot gnu.org
2024-01-02 17:59 ` 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-111485-4@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).