Do you think it is consistent behavior for array slicing?

[voroninp]

Guess the result of operations.

// 1
new []{1, 2, 3, 4, 5, 6, 7, 8, 9, 0}[10..];

// 2
new []{1, 2, 3, 4, 5, 6, 7, 8, 9, 0}[11..];

[bartonjs]

1. Empty array. (Make a copy of the array starting after elements[9] (the 10th item))
2. ArgumentOutOfRangeException (Make a copy of the array starting after elements[10] (the 11th item))

Slicing happens "between" elements. Slicing 10 means skip the first 10 items. In the case of a length 11+ collection that would mean "cut it between 10 and 11", but equally valid is "cut it after 10". Cutting after 10 for a 10-item collection means "return an empty collection".

Slicing 11 means "skip the first 11 items". In the case of a 10 item collection it throws an exception to represent "I can't find the 11th item".

[voroninp]

Then it is surprising that this behavior is not equivalent to Skip(x).Take(y) which is mentioned in docs.
Compare to F#'s behavior