Further, purity is about expectations, not scope. Expecting something to be pure means I can reliably call it with the same arguments and always get the same result, with the additional expectation that it will change nothing about the world. A function that accepts no arguments can be pure but must always return the same thing. If the person's name is indeed immutable, then person.getName(), provided it performs no side effects, is perfectly pure.
In concept, other than brevity, invoking a constructor on an immutable object is not much different than the function returned by a higher order function such as this:
(defn name-getter [{name :name}] (fn [] name)) (def get-name (name-getter {:name "John"})) (get-name)
person.getName() is the same as getName(person). In the former it's an implicit parameter, in the latter it's explicit. Or, looking at it differently, one is a syntax for functional calls that prepends the first argument as a target, and one is a syntax that accepts the target as the first argument.
With Java 8 method references, you can see this a bit more clearly. You could, for instance, do this to get a function without the implicit this:
Function<Person, String> getName = Person::getName; getName.apply(new Person());
def getName():
. . this.setName('foo')
. . return this.name
There's nothing in principle preventing you from doing that in the "functional" approach but if your data is immutable then you can't do it.
def getName(person):
person.setName('foo')
return person.name
The problem, from a functional viewpoint, isn't the implicit argument, it is the fact that you can write setName.