In the unit test for _.max() several assertions had the 'actual' and 'expected' parameters swapped. Fixed it yields the same result, but looks more consistent and potentially less confusing (a colleague actually got confused by this and we spent some time figuring out if there's a specific reason for them being swapped, concluding there isn't - hence this PR).
In the unit test for _.max() several assertions had the 'actual' and 'expected' parameters swapped. Fixed it yields the same result, but looks more consistent and potentially less confusing (a colleague actually got confused by this and we spent some time figuring out if there's a specific reason for them being swapped, concluding there isn't - hence this PR).