public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99586] New: Use of class template identifier checked for CTAD before instantiation Date: Sun, 14 Mar 2021 23:21:25 +0000 [thread overview] Message-ID: <bug-99586-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99586 Bug ID: 99586 Summary: Use of class template identifier checked for CTAD before instantiation Product: gcc Version: 11.0 URL: https://godbolt.org/z/4KWWjT Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: johelegp at gmail dot com CC: johelegp at gmail dot com Target Milestone: --- See https://godbolt.org/z/4KWWjT. ```C++ #include<array> template<auto>struct A{}; template<auto... V>A a=A<std::array{V...}>{}; ```
next reply other threads:[~2021-03-14 23:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-14 23:21 johelegp at gmail dot com [this message] 2021-03-15 17:34 ` [Bug c++/99586] " mpolacek at gcc dot gnu.org 2021-04-01 13:37 ` ppalka at gcc dot gnu.org 2021-04-02 23:57 ` cvs-commit at gcc dot gnu.org 2021-04-21 13:29 ` ppalka at gcc dot gnu.org 2021-04-21 23:18 ` johelegp at gmail dot com
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-99586-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: linkBe 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).