> My preference would be for there to be only one Self, and have it always be > the dynamic type of 'self'. Some people disagree, but I don't think it's all > that onerous to have to write ClassName.foo if that's really what you > specifically mean.
+1. There's just no way we want to explain two kinds of Selves to people. However, we need to make sure it works in these contexts: 1) #selector 2) getting an unbound method 3) referring to static methods (including private ones) A.
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
