Range is inclusive on both ends

[Maltysen]

Current Behavior

cheddar> 4:4
 [4]
cheddar> 2:10
 [2, 3, 4, 5, 6, 7, 8, 9, 10]

Desired Behavior

2:10 giving [2,3,4,5,6,7,8,9] and 4:4 giving []

because now, 0:n has a length of n+1, not n

[ConorOBrien-Foxx]

I don't see why this is a problem.

[Maltysen]

@ConorOBrien-Foxx array indexing, (I'm guessing, based on js) will be 0-indexed, so the ranges should also be 0-indexed, which means that the end should not be inclusive.

[ConorOBrien-Foxx]

Why does that follow ?

[Maltysen]

@ConorOBrien-Foxx what happens when you want to loop through an array of len n? the indices of that array are 0..n-1 other langs have inclusive range, but then they need to make everything 1-indexed. (example, APL)

[ConorOBrien-Foxx]

Okay? I still don't see your point. In a range m:n, n is often not the length of the range.

[Maltysen]

@ConorOBrien-Foxx but you will be indexing up to n for that array, but the last index is n-1, so the last number returned from : should be n-1

[ConorOBrien-Foxx]

Could you maybe rephrase? Perhaps I'll understand then.

[Maltysen]

@ConorOBrien-Foxx http://stackoverflow.com/questions/4504662/why-does-rangestart-end-not-include-end

[ConorOBrien-Foxx]

Oh, I see. It's customary.

[ConorOBrien-Foxx]

Fixed by making monadic range do this.