Comments on: C# lambdas: How much context should you need?

By: Dave Cameron

Dave Cameron — Thu, 01 Jan 2009 03:50:23 +0000

Especially since foo is here part of a much larger line of code, I like foo. In the SmallTalk code I’ve seen, it was convention to have a role-revealing name for block variables expressing what the block author thought the block was going to receive. Even for very short blocks like

eachFoo => return eachFoo.ToString();

By: Eric Jablow

Eric Jablow — Mon, 29 Dec 2008 20:43:31 +0000

The name ‘x’ is idiomatic for lambda variables, but I would it because I tend to reserve that name for the Cartesian coordinate or the real part of a complex number.

I think it depends; could you imagine using that lambda expression for items other than ‘Foo’ instances? Here, you could certainly inagine that, and so I would use a generic name like ‘item’ or ‘elem’. If the lambda expression depended on the variable being of type ‘Foo’, I would use a specific name.

By: Reflective Perspective - Chris Alcock » The Morning Brew #252

Reflective Perspective - Chris Alcock » The Morning Brew #252 — Mon, 29 Dec 2008 11:34:06 +0000

[...] C# lambdas: How much context should you need? – Mark Needham considers one of the important questions when it comes to lambda expressions, how clear is it when you use the (x -> x.blah) notation, so we need to be more careful about our choice of name for x to improve clarity. [...]

By: Chris Missal

Chris Missal — Sun, 28 Dec 2008 19:02:07 +0000

I don’t like to use ‘x’ because it’s non descriptive, but I do like its brevity. I typically would use ‘o’ on object Order or ‘os’ on object OrderService. It’s still brief, but slightly more helpful to recognize the object being used.

By: Arjan`s World » LINKBLOG for December 27, 2008

Arjan`s World » LINKBLOG for December 27, 2008 — Sat, 27 Dec 2008 21:00:31 +0000

[...] C# lambdas: How much context should you need? – Mark Needham [...]