Ooh, this is a fun find; what is happening here is that your local is getting optimized away – there are no locals remaining, which means that there is no .locals init, which means that stackalloc behaves differently, and does not wipe the space; private static unsafe uint Reinterpret1() { byte* bytes = stackalloc byte[4]; … Read more
The Span<T> / ref feature is essentially a series of rules about to which scope a given value can escape by value or by reference. While this is written in terms of method scopes it’s helpful to simplify to just one of two statements: The value cannot be returned from the method The value can … Read more
The sole reason to use stackalloc is performance (either for computations or interop). By using stackalloc instead of a heap allocated array, you create less GC pressure (the GC needs to run less), you don’t need to pin the arrays down, it’s faster to allocate than a heap array, an it is automatically freed on … Read more