oversight with input ranges

Jesse Phillips via Digitalmars-d digitalmars-d at puremagic.com
Tue Apr 21 20:00:18 PDT 2015


On Tuesday, 21 April 2015 at 19:53:47 UTC, ketmar wrote:
> here's the interesting oversight for isInputRange:
> https://issues.dlang.org/show_bug.cgi?id=14478
>
> so be careful: ranges with non-copyable elements aren't input 
> ranges for
> now. ;-)


The problem with allowing the inability to copy elements to be an 
input range is that you must then preven an algorithm from 
copying the range elements, how do you do that without preventing 
input ranges from having copyable elements?


More information about the Digitalmars-d mailing list