public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dan.raviv at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/106239] New: vector::resize(size_type, const value_type&) should not require copy-assignability Date: Sat, 09 Jul 2022 03:40:16 +0000 [thread overview] Message-ID: <bug-106239-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106239 Bug ID: 106239 Summary: vector::resize(size_type, const value_type&) should not require copy-assignability Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: dan.raviv at gmail dot com Target Milestone: --- Copy-constructibility should be enough. Related to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83981 https://godbolt.org/z/a1sYxThxG Compiles on Clang but not GCC: #include <vector> class C { const int m_x; public: C(int x) : m_x (x) {} }; int main() { auto v = std::vector<C>(10, C(42)); // v.resize(11); // Correctly does not compile v.resize(11, C(42)); // Incorrectly does not compile on GCC }
next reply other threads:[~2022-07-09 3:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-09 3:40 dan.raviv at gmail dot com [this message] 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 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@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).