he/him 
Swift solves this by optionally letting you declare what the exposed name of a parameter should be. This way a parameter can be called in a way internally, but then expose a perhaps more meaningful name to the user (and also allow for breaking changes internally)
Your parameter names then become an implicit public API making it a significant refactoring hazard. Would also lead to significant inconsistency across a codebase for when they’re used.
-
-
This Tweet is unavailable.
- 1 more reply
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.