Conversation
|
is not ExpressionFilter a reasonable alternative? On Aug 1, 2013, at 11:15 AM, adamcataldo notifications@github.com wrote:
Chris K Wensel |
|
You can, but we generally avoid ExpressionFilter at my company (Wealthfront), because we put a premium on having the compiler catch as many errors as possible. The expression is just a string, so the compiler isn't able to infer much. As a result, we tend to create more narrowly-focused filters, which is a bit more up-front work, but lends itself more easily to testing, which we also put a premium on. I've found myself using this particular filter often enough, that it seemed worth adding to the framework. In my mind, it's on par with FilterNull/FilterNotNull. |
No description provided.