Ranges help

Xinok xinok at live.com
Wed Oct 12 13:30:03 PDT 2011


On 10/12/2011 4:04 PM, Dmitry Olshansky wrote:
> On 12.10.2011 22:23, Xinok wrote:
>> I also need to figure out the template constraints. Would this be
>> correct? Or would this be too much?
>>
>> isRandomAccessRange && !isFiniteRange && isBidirectionalRange &&
>> hasSlicing
> isRandomAccessRange should be enough. Also why !isFinite how would one
> sort infinite range? hasSlicing is needed though. So my take on this
> would be:
> isRandomAccessRange && hasSlicing
>

Sorry, typo. That should be !isInfiniteRange. But I can drop 
!isInfinteRange anyways, so:

isRandomAccessRange && isBidirectionalRange && hasSlicing

isRandomAccessRange can be a bidirectional range or an infinite forward 
range, so isBidirectionalRange is still required.


More information about the Digitalmars-d-learn mailing list