News for hackers. Stuff that matters.
Re:Announcing .NET Core 2.1 by zamalek on Wednesday May 30, 2018 @08:48PM (#17193142)
Span (safely refers to data anywhere) and Memory (safely refers to data on the heap only) have a much nicer API than arrays. ArraySegment has had a facelift but to nit: ArraySegment is a pain to type. Also, unlike arrays, there are read-only variants - which are good for rich type checking. In addition you can easily reinterpret cast between blittable types (the new 'unmanaged' generic constraint) for when you are participating in mortal sins such as directly serializing byte representations.

Tons of reasons to use them besides performance. We use them for those reasons and if there is a performance boon, great bonus!

Re:Announcing .NET Core 2.1 by nlawalker on Thursday May 31, 2018 @08:56AM (#17195897)
This appears to imply that for brand new code with no dependencies, arrays are essentially obsoleted by Span/Memory. Is that a fair statement?
Re:Announcing .NET Core 2.1 by zamalek on Thursday May 31, 2018 @11:26AM (#17197006)
Mostly, yes.