Spanification
summary
Explains what Span<T> and Memory<T> actually do in .NET Core 2.1 and how they reduce allocations: slice without allocation, works as a lightweight pointer-like struct (ReadOnlySpan<T> / Span<T>), and requires compiler/runtime support so spans never live on the heap. Shows concrete tools—MemoryPool, pooled buffers and memory extensions—used to parse gigabyte text files and numbers in-place, cutting GC pressure and shaving about 25% off parse time in a demo. Notes limitations (no spanning async/await, short lifetimes) and practical workarounds.
AI-written summary · about
chapters (6)
related talks
01h 01mBoosting memory management in interoperability scenarios
52mPerformance features in C#
56mState of the .NET Performance
59mHigh-performance code design patterns in C#
01h 14mTurbocharged: Writing High-performance C# and .NET code
01h 04mTurbocharged: Writing High-Performance C# and .NET Code
01h 01mTurbocharged: Writing High-Performance C# and .NET Code
01h 01mWhat's new in .NET 9 & C# 13