> The explicit nil in the original implementation implies that the method is being called for its return value This kind of insight into the dev mind/process i

> The explicit nil in the original implementation implies that the method is being called for its return value This kind of insight into the dev mind/process is interesting b/c it shows how code is actually consumed. It also reveals where the implicit logic exists, so we can consider if it should be more explicit - in this case if functions should declare return types.