We all like playing around with working with Expression Trees, right? Creating type-safe functions at runtime when you don't know the types at compile time gives you great performance and is just plain neat. I'm using them in my pet object-object mapper, and need to look at the mapping functions it creates. Unfortunately, the default debug view for an Expression Tree looks something like this:

…now maybe you're some coding savant who eats IL for breakfast, but I find that pretty unreadable.

So! To get a nicer look at my Expression Trees, I've written ReadableExpressions, a PCL with a single extension method which translates an Expression Tree into something friendlier, like: