> function names are not subject to rot

I don't agree with this. I think often a function will drift from its name if functionality is added to an aspect of its implementation or because of refactoring.

And thus it's important to also rename things when refactoring, or else you get awful confused when your Foobinator(x) function returns you a Splunkinated value, or your FrobbleTheFribbets() call also woggles the wiggles.

>Function names are precisely encapsulation of the intent of the function

that's a rosy way to say, names entail a message.

An Address can also be computed, your argument is invalid.