this post was originally published on my Github Pages site on September 15th, 2017
This might sound a bit outlandish or ridiculous, but I seldom write loops nowadays. What I have found is that just about every programming language includes a set of methods or applicable functions that can replace just about every loop that I was previously writing. These higher-order functions are called map, filter, and fold.
filter function takes a predicate, a function which accepts an item from your array and returns a boolean result, and returns a new array containing the elements that return true when passed through the predicate.
We'll start off with some easy examples:
Unlike its counterparts map and fold, filter's name immediately and obviously expresses what it does. Though it's a rather simple function, it is very powerful nonetheless.
Here's an example of filtering an array of objects:
In the first filter, we are looking for people in the list whose name is Mary. Since there is only one person in the list with this name, we only get one result. Note that since
filter always returns an array, we just got back an empty array when we looked for someone named Fred in the second filter. In the third example, we look for people whose age is greater than 40. Finally, in the last example, we look for people who have two hobbies.
If this is taking a bit to click, I'll show an example of
filter done in an imperative style. This is a pattern I used to write quite often before I knew how to use filter.
While these loops have the same result as the previous examples, they are much more explicit and there is much more typing involved.
These examples are pretty easy, right? Well, there really isn't a whole lot to it.
Out of the map-filter-fold family of functions,
When I am filtering data based on multiple conditions, I like to define the predicates as named variables ahead of time. I've found that this improves the readability of the code tremendously, in addition to providing opportunities to reusing the pre-defined functions. Consider the following example:
filter always returns an array, you can chain together your calls to
filter and drill down to the data you want incrementally. You must be careful with your logic, though, especially when the filtering logic you are trying to apply requires mixing AND and OR logic.
This might not need to be said, but you should use
filter when you want to reduce the items in a collection to only those items which meet specific criteria.
Pretty much all the good ones. Though the names might be a bit different. In an effort to avoid plagiarism and only write what I really know about, I'll list out a few equivalent methods/functions that I know and have used here.
|C#||IEnumerable.Where (as part of System.Linq)|
Right now! Go!
The best way to get familiar with
filter is to just start using it.