From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: New istreambuf_iterator debug check
Date: Mon, 29 Jan 2018 15:45:00 -0000 [thread overview]
Message-ID: <20180129135209.GN3417@redhat.com> (raw)
In-Reply-To: <e54204f1-ece7-319d-095e-a5380f5a262c@gmail.com>
On 24/01/18 17:39 +0100, François Dumont wrote:
>Hi
>
>Â Â Â I'd like to propose this new debug check. Comparing with non-eos
>istreambuf_iterator sounds like an obvious coding mistake.
Agreed, but that doesn't mean we can terminate the process. It's still
valid C++, even though it's probably not what the author intended to do.
prev parent reply other threads:[~2018-01-29 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 16:46 François Dumont
2018-01-24 18:35 ` Petr Ovtchenkov
2018-01-24 21:29 ` François Dumont
2018-01-25 9:04 ` Petr Ovtchenkov
2018-01-29 15:45 ` Jonathan Wakely [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=20180129135209.GN3417@redhat.com \
--to=jwakely@redhat.com \
--cc=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).