LINQ naming Standard - Lambda Expression [duplicate]

Question

We normally follow coding / naming standard for all C# syntax. For Example, if we declare string inside the method, we use Scope-datatype-FieldName format. (lstrPersonName)

List<Person> icolPerson;
private LoadPersonName()
{
   string lstrPersonaName;
}

i am kind of thinking how do we follow the naming standard in Lambda Expression. Especially when we defined the arguments for func delegate, we use shorted names like x. For Example

var lobjPerson = icolPerson.Where(x => x.person_id = 100)

if you look at the above line, X does not follow any standard. i also read that one purpose of lambda expression is to reduce the lenghthy code.

i am here to seek help to get the right approach for naming standard.

var lobjPerson = icolPerson.Where(x => x.person_id = 100)

OR

var lobjPerson = icolPerson.Where(lobjPerson => lobjPerson .person_id = 100)

Answer 1

My lambdas use one letter arguments, usually the first letter of what the parameter name would be:

• buttons.Select(b => b.Text);

• services.Select(s => s.Type);

But sometimes I add a few more letters to make things clearer, or to disambiguate between two parameters.

And when there isn't much meaning attached to the things I use xs and ys:

• values.Aggregate((x, y) => x + y);

All said, the standard I use for lambdas is shortness first, expressiveness later, because the context tends to help understand things (in the first example it's obvious that the b stands for a button).