public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/106749] New: Implement C++23 library features
Date: Fri, 26 Aug 2022 08:53:46 +0000	[thread overview]
Message-ID: <bug-106749-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106749
           Summary: Implement C++23 library features
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: meta-bug
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: redi at gcc dot gnu.org
  Target Milestone: ---

A meta bug to track the overall progress of C++23 features in the C++ standard
library.

             reply	other threads:[~2022-08-26  8:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  8:53 redi at gcc dot gnu.org [this message]
2022-08-26  8:58 ` [Bug libstdc++/106749] " redi at gcc dot gnu.org
2022-08-26 20:13 ` mpolacek at gcc dot gnu.org
2022-10-03 14:51 ` redi at gcc dot gnu.org
2022-11-19  9:24 ` jakub at gcc dot gnu.org
2023-11-16  8:14 ` redi at gcc dot gnu.org
2023-12-15  0:04 ` redi at gcc dot gnu.org
2024-01-10 15:00 ` ppalka at gcc dot gnu.org
2024-01-12 20:39 ` redi at gcc dot gnu.org
2024-01-13  4:06 ` ppalka at gcc dot gnu.org
2024-01-13 11:22 ` redi at gcc dot gnu.org
2024-01-17 16:51 ` redi at gcc dot gnu.org
2024-02-01 20:04 ` ppalka at gcc dot gnu.org
2024-02-02 14:43 ` redi at gcc dot gnu.org
2024-04-15 18:33 ` redi 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-106749-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).