public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yihuajack at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113160] Const valarray (g)slice and indirect_array fail to match valarray in template functions Date: Sat, 30 Dec 2023 14:06:31 +0000 [thread overview] Message-ID: <bug-113160-4-sSbj2TPY5d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113160-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113160 --- Comment #5 from Yihua Liu <yihuajack at gmail dot com> --- I see. Previous cppreference notes were misleading. Is there any plan to support returning a std::valarray or matching a std::valarray? For example, if it returns a std::valarray, it can be directly put in a pipe syntax.
prev parent reply other threads:[~2023-12-30 14:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-28 4:11 [Bug libstdc++/113160] New: " yihuajack at gmail dot com 2023-12-28 5:00 ` [Bug libstdc++/113160] " pinskia at gcc dot gnu.org 2023-12-28 6:19 ` yihuajack at gmail dot com 2023-12-28 18:44 ` redi at gcc dot gnu.org 2023-12-28 18:46 ` redi at gcc dot gnu.org 2023-12-30 14:06 ` yihuajack at gmail dot com [this message]
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-113160-4-sSbj2TPY5d@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).