Comments on: Array Slicing in C#

By: Vladimir Pecanac

Vladimir Pecanac — Sat, 12 Mar 2022 11:25:28 +0000

In reply to Magomed Mirzaev. That's right Magomed. For those wondering, we can do this now:

var listOfNumbers = new List<int>()
{
	1, 2, 3, 4, 5, 6, 7
};

var bla = listOfNumbers.Skip(2).Take(2..4);

The result would be 5, 6.

By: Magomed Mirzaev

Magomed Mirzaev — Sat, 12 Mar 2022 10:27:44 +0000

Since C# 10 we can pass range to the Take method of LINQ

By: Marinko Spasojević

Marinko Spasojević — Fri, 11 Mar 2022 16:56:25 +0000

In reply to Joel.

Thank you Joel a lot. Those are great suggestions and we have updated the article, you just need to refresh the page if you can’t see the updates (due to caching). Just regarding the part you are not agreeing with – I agree with you, we just didn’t mention Span here so we didn’t choose it over ReadOnlySpan. But, we fixed that. It should be mentioned.

By: Joel

Joel — Thu, 10 Mar 2022 15:42:28 +0000

It's probably worth mentioning that the Range Operator approach allocates new arrays when you use it on an array, and does not when you use it on a Span. "However, we might have some other algorithms that update our data regularly, in this case, we should use ArraySegment." I disagree with this. If you need to update data, use Span<T> instead of ReadOnlySpan<T>. There's few if any scenarios where ArraySegment is better than Span.