Previously we discovered how to hold an unboxed instance of System.Void, and although circumventing the .NET framework always feels good, it left us with a burning question; What does the memory layout look like? Can a class contain infinite voids?

Previously we have show how we can obtain an instance of System.Void, despite some effort by the .NET team to disallow that. However the API we used returned an object which led to the boxing of the void instance. Having a box of nothing is not the same as having nothing, so it seems like we must take an alternative route so that we can finally hold an unboxed void.

In the last post I discussed how System.Void is meant as a placeholder and not meant to actually be instantiated. Being of a rebellious nature, I need no more motivation than that to want to instantiate one. However the .NET team has made some effort to stop attempts to create voids.

However if I really wanted one of these delicious voids, could I get one?

I've recently been taking an interest in the System.Void type. It's an illegal type to reference in C#, so why does it exist?

Hi! If you're reading this it means that I've finally finished coding up my blog and have found a friendly hosting service. I started this site as a personal challenge - I love learning new things and explaining things as I learn; doing that so openly should prove to be an exciting new adventure!