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++/92103] constraints not checked on nested class template
Date: Wed, 25 Nov 2020 18:10:59 +0000	[thread overview]
Message-ID: <bug-92103-4-xEmflz444h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92103-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:2fe01dcd25d29798510101303b5bbfc254003b18

commit r10-9080-g2fe01dcd25d29798510101303b5bbfc254003b18
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Jun 4 23:20:49 2020 +0100

    libstdc++: Remove workarounds for constrained nested class templates

    With PR c++/92078 and PR c++/92103 both fixed, nested class templates
    can now be constrained. That means a number of namespace-scope helpers
    can be moved to the class scope, so they're only visible where they're
    needed.

            * include/bits/iterator_concepts.h (__detail::__ptr,
__detail::__ref)
            (__detail::__cat, __detail::__diff): Move to class scope in the
            relevant __iterator_traits specializations.
            (__iterator_traits<>): Use nested class templates instead of ones
from
            namespace __detail.
            * include/bits/stl_iterator.h (__detail::__common_iter_ptr): Move
to
            class scope in iterator_traits<common_iterator<I, S>>.
            (iterator_traits<common_iterator<I, S>>): Use nested class template
            instead of __detail::__common_iter_ptr.

    (cherry picked from commit f2242ec0d3f1bb13c78ef3c21e0354d84fe57222)

      parent reply	other threads:[~2020-11-25 18:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92103-4@http.gcc.gnu.org/bugzilla/>
2020-06-02 19:15 ` ppalka at gcc dot gnu.org
2020-06-03 20:41 ` cvs-commit at gcc dot gnu.org
2020-06-04 17:21 ` cvs-commit at gcc dot gnu.org
2020-06-04 17:22 ` ppalka at gcc dot gnu.org
2020-06-04 22:34 ` cvs-commit at gcc dot gnu.org
2020-11-25 18:10 ` cvs-commit 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-92103-4-xEmflz444h@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).