public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98940] Implement C++23 language features
Date: Thu, 18 Nov 2021 23:11:09 +0000 [thread overview]
Message-ID: <bug-98940-4-u59F76HfRO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98940-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98940
Bug 98940 depends on bug 103049, which changed state.
Bug 103049 Summary: [C++23] P0849R8 - auto(x): decay-copy in the language
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103049
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
next prev parent reply other threads:[~2021-11-18 23:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 19:48 [Bug c++/98940] New: " mpolacek at gcc dot gnu.org
2021-02-02 19:48 ` [Bug c++/98940] " mpolacek at gcc dot gnu.org
2021-02-03 20:00 ` mpolacek at gcc dot gnu.org
2021-03-25 15:58 ` mpolacek at gcc dot gnu.org
2021-06-11 14:02 ` jakub at gcc dot gnu.org
2021-06-30 16:19 ` mpolacek at gcc dot gnu.org
2021-07-19 13:59 ` mpolacek at gcc dot gnu.org
2021-09-01 20:38 ` jakub at gcc dot gnu.org
2021-10-06 8:27 ` jakub at gcc dot gnu.org
2021-10-06 9:12 ` jakub at gcc dot gnu.org
2021-10-07 13:24 ` jakub at gcc dot gnu.org
2021-10-26 15:44 ` mpolacek at gcc dot gnu.org
2021-11-18 23:11 ` mpolacek at gcc dot gnu.org [this message]
2021-11-25 7:42 ` jakub at gcc dot gnu.org
2022-05-09 20:02 ` mpolacek at gcc dot gnu.org
2022-07-15 15:35 ` mpolacek at gcc dot gnu.org
2022-08-24 8:05 ` jakub at gcc dot gnu.org
2022-08-26 7:32 ` jakub at gcc dot gnu.org
2022-08-26 14:08 ` jakub at gcc dot gnu.org
2022-09-01 9:42 ` jakub at gcc dot gnu.org
2022-09-26 17:42 ` mpolacek at gcc dot gnu.org
2022-09-27 11:00 ` redi at gcc dot gnu.org
2022-09-27 23:40 ` mpolacek at gcc dot gnu.org
2022-11-04 17:29 ` jakub at gcc dot gnu.org
2022-11-08 1:37 ` mpolacek at gcc dot gnu.org
2022-11-16 21:36 ` mpolacek at gcc dot gnu.org
2022-11-19 9:21 ` jakub at gcc dot gnu.org
2022-11-19 9:24 ` jakub at gcc dot gnu.org
2022-11-19 9:24 ` jakub at gcc dot gnu.org
2022-11-19 9:25 ` jakub at gcc dot gnu.org
2023-11-29 22:24 ` mpolacek at gcc dot gnu.org
2023-12-05 0:45 ` mpolacek at gcc dot gnu.org
2024-01-03 15:06 ` 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-98940-4-u59F76HfRO@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).