Handler code wrapped in @(...)?

In the second step, the event handler code is wrapped in an additional @(...) construct:

@onclick="@(() => Console.WriteLine(special.Name))"

Can you explain why? It seems to work without problems with just

@onclick="() => Console.WriteLine(special.Name))"

[jessegood]

@lohithgn To me, the current examples are not consistent though in there use of parentheses:

Without parentheses: <span class="topping-price">@topping.Topping.GetFormattedPrice()</span>

With parentheses: Price: <span class="price">@(Pizza.GetFormattedTotalPrice())</span>

With and without? <div class="title">@(Pizza.Size)" @Pizza.Special.Name</div>

When you say opt for explicit razor expressions, what are your guidelines for using them?

[jessegood]

@jessegood I see. Let me try to explain again. Basically, I would prefer implicit expressions over explicit unless the parser requires them. So in the example that you copied from my question, I would make it: <span class="price">@Pizza.GetFormattedTotalPrice()</span> and not <span class="price">@(Pizza.GetFormattedTotalPrice())</span>

My question was why prefer the latter over the former, as it doesn’t make the code easier to understand.