protocol for using InputRanges

Walter Bright newshound2 at digitalmars.com
Thu Mar 27 13:53:35 PDT 2014


On 3/27/2014 9:12 AM, monarch_dodra wrote:
> If you initialized the next element in both constructor

As mentioned earlier, requiring this of a range constructor makes it impossible 
to separate composition of a range with using it.

As also mentioned earlier, this throws under the bus entire categories of use 
cases for ranges, all to avoid a single call to 'empty'.



More information about the Digitalmars-d mailing list