It’s confusing to have a class member with the same name (case differences aside) as its enclosing class. This is particularly so when you consider
the common practice of naming a class instance for the class itself.
Best practice dictates that any field or member with the same name as the enclosing class be renamed to be more descriptive of the particular
aspect of the class it represents or holds.
Noncompliant code example
public class Foo {
private var foo : String
public func getFoo() -> String {
return foo
}
//...
}
var foo = Foo()
foo.getFoo() // what does this return?
Compliant solution
public class Foo {
private var name : String
public func getName() -> String {
return name
}
//...
}
var foo = Foo();
foo.getName()
