Learning Functional Programming in Go

What's wrong with a function signature with more than seven parameters?

A function signature should not be so long and complicated that we are unable to comprehend it. Keep it simple. Use thoughtful, reasonable, and meaningful parameter names.

Ever noticed that functions with a long parameter list are typically some type of constructor? And that those functions are prone to get even more parameters over time?

It is natural for software engineers to want to reduce their functions' parameter lists. That's part of what we do when we refactor our application. As long as we keep the goal of comprehensibility in mind, we'll be fine. Sometimes, we ...