This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [RFC] libstdc++/14039 or std::find vs input_iterator requirements
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Paolo Carlini <pcarlini at suse dot de>
- Cc: libstdc++ <libstdc++ at gcc dot gnu dot org>
- Date: 06 Feb 2004 11:51:26 +0100
- Subject: Re: [RFC] libstdc++/14039 or std::find vs input_iterator requirements
- Organization: Integrable Solutions
- References: <402369C7.8050301@suse.de>
Paolo Carlini <pcarlini@suse.de> writes:
| Hi everyone,
|
| Jeremy point out that:
|
| "The expression (*__first == __val) appears in the implementation
| std::find. However, __first is only required to be an input iterator,
| so *__first is required to be convertible to the value type
| but not necessarily comparable with the value type."
|
| However, 25.1.2, p2 explicitly talks about: "... *i == value,..."
| and 244 (NAD) shows a typical implementation that exactly presents
| the same "problem" of ours.
|
| Indeed, I get Jeremy's fine technical point, but shall we actually
| take action missing a clarification in the standard??
I think that is streching wording and the implementation too far.
Let's keep simple things, simple.
-- Gaby