ASP.NET MVC Html.XXFor OK to discard lambda argument and just use Model directly? I find it a bit odd in ASP.NET MVC that the Html helper extensions, like Html.EditorFor, take a Func&lt;T1, TResult&gt; where the T1 argument is just the already in scope Model variable, e.g.:

@Html.EditorFor(x =&gt; x.Name)


If I really wanted Model renamed, I would just assign it once to a variable in the top of the razor view. So, I feel compelled to do the following:

@Html.EditorFor(_ =&gt; Model.Name)


Does this seem reasonable?
I'd fail this review if I saw it at my company.  Most are probably shown the first approach, doing this will only confuse people that come after you.  Now they have to determine if the way you've chosen is actually equivolent to the "standard" way.  I actually just went through that exercise myself.