public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/106239] vector::resize(size_type, const value_type&) should not require copy-assignability Date: Sat, 09 Jul 2022 05:54:36 +0000 [thread overview] Message-ID: <bug-106239-4-irAAf5eFWd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106239-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106239 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- https://cplusplus.github.io/LWG/issue2033 Officially made it CopyInsertable: Requires: T shall be MoveInsertable into *this and CopyInsertable into *this. CopyInsertable is basically: ::new((void*)p) T(v) (for pre c++20). So yes it would be invalid.
next prev parent reply other threads:[~2022-07-09 5:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-09 3:40 [Bug libstdc++/106239] New: " dan.raviv at gmail dot com 2022-07-09 5:49 ` [Bug libstdc++/106239] " pinskia at gcc dot gnu.org 2022-07-09 5:54 ` pinskia at gcc dot gnu.org [this message] 2022-07-09 11:13 ` redi at gcc dot gnu.org 2022-07-09 17:03 ` dan.raviv at gmail dot com 2023-02-08 11:27 ` redi at gcc dot gnu.org 2023-02-16 12:53 ` 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-106239-4-irAAf5eFWd@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: linkBe 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).