public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92944] [concepts] redefinition error when using constrained structure template inside namespace
Date: Thu, 27 Jan 2022 16:02:17 +0000	[thread overview]
Message-ID: <bug-92944-4-l2Tt0E8M1H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92944-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:ce6054a22ae14594a2919d2ad87cd9478e616fb3

commit r12-6896-gce6054a22ae14594a2919d2ad87cd9478e616fb3
Author: Patrick Palka <ppalka@redhat.com>
Date:   Thu Jan 27 10:56:34 2022 -0500

    c++: constrained partial spec using qualified name [PR92944, PR103678]

    In the nested_name_specifier branch within cp_parser_class_head, we need
    to update 'type' with the result of maybe_process_partial_specialization
    like we do in the template_id_p branch.

            PR c++/92944
            PR c++/103678

    gcc/cp/ChangeLog:

            * parser.cc (cp_parser_class_head): Update 'type' with the result
            of maybe_process_partial_specialization in the
            nested_name_specifier branch.  Refactor nearby code to accomodate
            that maybe_process_partial_specialization returns a _TYPE, not a
            TYPE_DECL, and eliminate local variable 'class_type' in passing.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/concepts-partial-spec10.C: New test.
            * g++.dg/cpp2a/concepts-partial-spec11.C: New test.

  parent reply	other threads:[~2022-01-27 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92944-4@http.gcc.gnu.org/bugzilla/>
2020-07-29 13:32 ` redi at gcc dot gnu.org
2021-12-14 11:22 ` ed at catmur dot uk
2021-12-17 20:53 ` ed at catmur dot uk
2021-12-23 12:55 ` ppalka at gcc dot gnu.org
2021-12-28  9:29 ` pinskia at gcc dot gnu.org
2022-01-26 17:28 ` ppalka at gcc dot gnu.org
2022-01-27 16:02 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-27 16:04 ` 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-92944-4-l2Tt0E8M1H@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).