I know that methods declared with void
does not return anything.
But it seems that in C#, void
is more than just a keyword, but a real type.
void
is an alias for System.Void
, like int
that is for System.Int32
.
Why am I not allowed to use that type? It does not make any sense, but these are just some thoughts about the logic.
Neither
var nothing = new System.Void();
(which says I should use void
(Not an alias?))
nor
var nothing = new void();
compiles.
It is also not possible to use something like that:
void GiveMeNothing() { }
void GiveMeNothingAgain()
{
return GiveMeNothing();
}
So what's the point with System.Void
?
From the documentation:
The
Void
structure is used in theSystem.Reflection
namespace, but is rarely useful in a typical application. TheVoid
structure has no members other than the ones all types inherit from theObject
class.
There's no reason really to use it in code.
Also:
var nothing = new void();
This doesn't compile for me. What do you mean when saying it "works"?
Update:
A method void Foo()
does not return anything. System.Void
is there so that if you ask (through Reflection) "what is the type of the return value of that method?", you can get the answer typeof(System.Void)
. There is no technical reason it could not return null
instead, but that would introduce a special case in the Reflection API, and special cases are to be avoided if possible.
Finally, it is not legal for a program to contain the expression typeof(System.Void)
. However, that is a compiler-enforced restriction, not a CLR one. Indeed, if you try the allowed typeof(void)
and look at its value in the debugger, you will see it is the same value it would be if typeof(System.Void)
were legal.