[Issue 14478] isInputRange failed to recognize some ranges
via Digitalmars-d-bugs
digitalmars-d-bugs at puremagic.com
Tue Apr 21 15:51:43 PDT 2015
https://issues.dlang.org/show_bug.cgi?id=14478
Jonathan M Davis <issues.dlang at jmdavisProg.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |issues.dlang at jmdavisProg.co
| |m
--- Comment #3 from Jonathan M Davis <issues.dlang at jmdavisProg.com> ---
If
auto h = r.front;
doesn't work, then I don't think that it can be a range. And if that means
that elements have to be copyable to be in a range, then I think that
they're going to have to be copyable. There is going to be _way_ too much
code out there that does
auto h = r.front;
for it to work to try and claim that something is an input range when that
line doesn't work. And IIRC, C++ STL containers require that their elements
be copyable in order to work, so it's not like we'd be the first to require
this sort of thing.
--
More information about the Digitalmars-d-bugs
mailing list