public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/102358] New: niter_base and miter_base overloaded for move_iterator missing constexpr Date: Thu, 16 Sep 2021 07:38:52 +0000 [thread overview] Message-ID: <bug-102358-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102358 Bug ID: 102358 Summary: niter_base and miter_base overloaded for move_iterator missing constexpr Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: hewillk at gmail dot com Target Milestone: --- stl_iterator.h#L2416: template<typename _Iterator> auto __niter_base(move_iterator<_Iterator> __it) -> decltype(make_move_iterator(__niter_base(__it.base()))) { return make_move_iterator(__niter_base(__it.base())); } template<typename _Iterator> auto __miter_base(move_iterator<_Iterator> __it) -> decltype(__miter_base(__it.base())) { return __miter_base(__it.base()); } They seem to be missing constexpr: #include <algorithm> #include <array> constexpr bool b = [] { std::array<int, 2> in{}, out{}; std::move(std::move_iterator(in.begin()), std::move_iterator(in.end()), out.begin()); return true; }(); https://godbolt.org/z/PTrTnxTnK
next reply other threads:[~2021-09-16 7:38 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-16 7:38 hewillk at gmail dot com [this message] 2021-09-25 20:06 ` [Bug libstdc++/102358] " redi at gcc dot gnu.org 2021-10-21 12:31 ` ppalka at gcc dot gnu.org 2021-10-21 16:13 ` cvs-commit at gcc dot gnu.org 2022-02-16 21:43 ` gcc at ebasoft dot com.pl 2022-02-17 10:29 ` redi at gcc dot gnu.org 2022-02-17 10:53 ` gcc at ebasoft dot com.pl 2022-02-17 11:40 ` redi at gcc dot gnu.org 2022-02-17 11:50 ` gcc at ebasoft dot com.pl 2022-02-17 12:37 ` redi at gcc dot gnu.org 2022-02-17 13:03 ` cvs-commit at gcc dot gnu.org 2022-02-17 13:04 ` cvs-commit at gcc dot gnu.org 2022-02-17 13: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-102358-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).