> It’s really not as complicated as you’re making it out to be. Of course it's not complicated, it's as simple as I showed. > If I’m making a function that ha

> It’s really not as complicated as you’re making it out to be. Of course it's not complicated, it's as simple as I showed. > If I’m making a function that has potentially confusing parameters, I make it accept an object. It doesn't really matter what you, a single developer, do, does it? If I have to work with a third-party library that has "confusing parameters", please enlighten me how I can make its functions "accept an object to force named parameters"? > there’s no dedicated syntax to allow people to name parameters that weren’t intended to be named. So what? I've clearly shown what in at least three messages.