Introduction - If you have any usage issues, please Google them yourself
An Object Explorer Written in a Map/Filter style with C# Partial Application Functions
Recently I wanted to visually inspect the structure of an object created by some service, so I wrote a function that reflects over an object and builds a tree of the various class properties and drills into List<T> collections. Simple enough, but I thought, gee, this might be useful, I'd like to expand it to handle Dictionary<A, B>, enums, nullable property types, etc. The main recursive function ended up being a 130 line long sort of organized mess. Thinking about refactoring it into more manageable pieces, it occurred to me that all this code was basically an imperative implementation of map and filter operations.