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++/106803] views::adjacent_transform should not return views::empty<tuple<>> when N == 0
Date: Thu, 01 Sep 2022 16:43:18 +0000	[thread overview]
Message-ID: <bug-106803-4-eLnj8lyTJQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106803-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106803

--- Comment #1 from 康桓瑋 <hewillk at gmail dot com> ---
Another issue is that views::zip_transform returns
views::empty<decay_t<invoke_result_t<_Fp>>> when N == 0, which is not strictly
true, the standard requires that the return is the result of the *lvalue* F
being invoked, that is, views::empty<decay_t<invoke_result_t<decay_t<_Fp>&>>>.

  reply	other threads:[~2022-09-01 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 16:37 [Bug libstdc++/106803] New: " hewillk at gmail dot com
2022-09-01 16:43 ` hewillk at gmail dot com [this message]
2022-09-01 17:10 ` [Bug libstdc++/106803] " ppalka at gcc dot gnu.org
2022-09-09 19:05 ` cvs-commit at gcc dot gnu.org
2022-09-09 19:09 ` ppalka at gcc dot gnu.org
2022-09-10  3:39 ` hewillk at gmail dot com

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-106803-4-eLnj8lyTJQ@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: link
Be 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).