public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "victor.dyachenko at protonmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114147] tuple allocator-extended constructor requires non-explicit default constructor Date: Wed, 28 Feb 2024 10:48:57 +0000 [thread overview] Message-ID: <bug-114147-4-mXwKAlDOOM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114147-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114147 --- Comment #1 from __vic <victor.dyachenko at protonmail dot com> --- Why _ImplicitDefaultCtor is required here? template<typename _Alloc, _ImplicitDefaultCtor<is_object<_Alloc>::value, _T1, _T2> = true> _GLIBCXX20_CONSTEXPR tuple(allocator_arg_t __tag, const _Alloc& __a) : _Inherited(__tag, __a) { } Missing overload for explicit tuple(allocator_arg_t, ...)?
next prev parent reply other threads:[~2024-02-28 10:48 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-28 10:39 [Bug libstdc++/114147] New: " victor.dyachenko at protonmail dot com 2024-02-28 10:48 ` victor.dyachenko at protonmail dot com [this message] 2024-02-28 11:18 ` [Bug libstdc++/114147] " victor.dyachenko at protonmail dot com 2024-02-28 11:21 ` [Bug libstdc++/114147] [10/11/12/13 Regression] " redi at gcc dot gnu.org 2024-02-28 13:49 ` [Bug libstdc++/114147] [11/12/13 " victor.dyachenko at protonmail dot com 2024-02-28 14:31 ` [Bug libstdc++/114147] [11/12/13/14 " redi at gcc dot gnu.org 2024-02-29 20:38 ` redi at gcc dot gnu.org 2024-03-01 15:12 ` redi at gcc dot gnu.org 2024-03-04 20:25 ` cvs-commit at gcc dot gnu.org 2024-03-16 10:19 ` [Bug libstdc++/114147] [11/12/13 " cvs-commit at gcc dot gnu.org 2024-03-18 14:03 ` [Bug libstdc++/114147] [11/12 " cvs-commit at gcc dot gnu.org 2024-03-18 14:14 ` [Bug libstdc++/114147] [11 " redi at gcc dot gnu.org 2024-05-02 10:53 ` cvs-commit at gcc dot gnu.org 2024-05-02 10:54 ` 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-114147-4-mXwKAlDOOM@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).