public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106837] False compilation error "inconsistent begin/end types in range-based 'for' statement"
Date: Mon, 05 Sep 2022 13:22:10 +0000	[thread overview]
Message-ID: <bug-106837-4-qvgxGh3bCg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106837-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> In this case the begin/end iter types *are* comparable
Not exactly as the operator!= requires a lvalue. And end() is not an lvalue.

  reply	other threads:[~2022-09-05 13:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 13:17 [Bug c++/106837] New: " ofekshilon at gmail dot com
2022-09-05 13:22 ` pinskia at gcc dot gnu.org [this message]
2022-09-05 13:30 ` [Bug c++/106837] " ofekshilon at gmail dot com
2022-09-05 13:35 ` jakub at gcc dot gnu.org
2022-09-06  9:12 ` ofekshilon 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-106837-4-qvgxGh3bCg@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).