Doesn't that depend on what you consider your condition?
createSomething=function that creates something and returns true if correctly created and false otherwise
if(createSomething());
did that do nothing?
edit: perhaps nothing useful since we can't know the state returned by createSomething.
What's the point of having branching construct that uses different syntax for exactly one instruction than for many instructions?
And if you are crazy like that then why not have:
that does nothing? Oh. Wait. We have that in C, Java (not C# though). I guess consistency is not the be all and end all of language design.