Too Long; Didn't Read
In <a href="https://www.mmhaskell.com/blog/2017/6/19/profiling-in-haskell" target="_blank">last week’s article</a>, we used benchmarks to determine how well our code performs on certain inputs. First we used the Criterion library to get some measurements for our code. Then we were able to look at those measurements in some spiffy output. We also profiled our code to try to determine what part of our code was slowing us down.