public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104559] vector<bool> v; v.insert(v.begin()); compiles, but it shouldn't
Date: Wed, 16 Feb 2022 10:01:16 +0000	[thread overview]
Message-ID: <bug-104559-4-FLA5CeTD25@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104559-4@http.gcc.gnu.org/bugzilla/>

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

Jiang An <de34 at live dot cn> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |de34 at live dot cn

--- Comment #3 from Jiang An <de34 at live dot cn> ---
The default argument has been present in a very early (perhaps the first)
version of libstdc++. 
https://github.com/gcc-mirror/gcc/blob/6599da043e22e96ac830fb50a61c1b6d95d1b142/libstdc%2B%2B/stl/bvector.h#L472

AFIAK this default argument has never been a part of the C++ standard, but was
in in some prehistoric working drafts. Seems removed by WG21-N1051.
http://www.open-std.org/JTC1/SC22/WG21/docs/wp/html/cd2/lib-containers.html#lib.vector.bool
http://www.open-std.org/JTC1/SC22/WG21/docs/papers/1997/N1051.asc

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 22:31 [Bug libstdc++/104559] New: " arthur.j.odwyer at gmail dot com
2022-02-15 22:50 ` [Bug libstdc++/104559] " pinskia at gcc dot gnu.org
2022-02-16  9:32 ` redi at gcc dot gnu.org
2022-02-16 10:01 ` de34 at live dot cn [this message]
2022-02-17 10:48 ` redi at gcc dot gnu.org
2022-02-17 23:45 ` cvs-commit at gcc dot gnu.org
2022-02-17 23:46 ` redi at gcc dot gnu.org
2022-02-17 23:46 ` 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-104559-4-FLA5CeTD25@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).