Vaguely related to the lazy property problem. cc @jckarter, @slavapestov

Yes, arguably 'self' should have DynamicSelfType in all class methods, not just those returning self. Right now this cannot be enabled without introducing performance regressions, because of optimizer limitations. I'm going to re-title this bug because finally somebody cares about this issue (yay!). It's a lot more general than just properties.

@swift-ci create

Also arguably, this could use a proposal, since it's source breaking (in a very minor way).

Note that it does not impact ABI, so there's no real urgency to deal with it in the short term.

I don't think the retitling is correct. If you write a static function that reads foo it does the right thing.

class C {
  static var foo: String { return "\(self)" }
  static func bar() -> String { return foo }
}

class D : C {}

print(D.bar()) // D

@belkadan Hmm. So 'let foo = bar' in type context is type checked like 'let foo = C.bar', not 'let foo = type(of: self).bar'. The latter would be more consistent behavior if we also change methods to have a dynamic 'self' type.