Span<T> and friends are included in .NET Core 2.1, so no additional NuGet package needs to be installed. Dan Sorensen’s answer was correct at that date and based on the preview, but now it is outdated. For string, the extension methods are AsSpan and AsMemory, that return ReadOnlySpan<char> and ReadOnlyMemory<char> respectively. Explicit AsReadOnlySpan is gone, … Read more
If you really want to keep it returning default, you could use result.Equals(default) the built-in Equals method of a ValueTuple should work. As of C# 7.3 value tuples now also support comparisons via == and != fully, Meaning you can now also do result == default and it should work the same.
Before C# 7.2 we had protected internal modifier. This really means protected OR internal, that is – member A is accessible to child classes and also to any class in the current assembly, even if that class is not child of class A (so restriction implied by “protected” is relaxed). private protected really means protected … Read more
Span<T> is stack-only in nature while Memory<T> can exist on the heap. Span<T> is a new type we are adding to the platform to represent contiguous regions of arbitrary memory, with performance characteristics on par with T[]. Its APIs are similar to the array, but unlike arrays, it can point to either managed or native … Read more
in was recently introduced to the C# language. in is actually a ref readonly. Generally speaking, there is only one use case where in can be helpful: high performance apps dealing with lots of large readonly structs. Assuming you have: readonly struct VeryLarge { public readonly long Value1; public readonly long Value2; public long Compute() … Read more
Here are all access modifiers in Venn diagrams, from more limiting to more promiscuous: private: private protected: – added in C# 7.2 internal: protected: protected internal: public: