For reference, this seems to be similar to a bug we were having in Reusable, adding a storyboard type property to UIViewController but the compiler could not see it but only the instance property declared in UIKit

See GitHub issue here: AliSoftware/Reusable#33 (comment)

(not sure if the OP ended up filling Jira as I suggested them at that time?)

@swift-ci create

Comment by Graydon Hoare (JIRA)

Simplified testcase:

open class B {
    public var a: Int? = nil
}

import M
class C: B {
     func foo() {
    self.a = 0
     }
    static let a: Int = 0
}

Then run:

$ swiftc -module-name M -emit-module file1.swift
$ swiftc -I . file2.swift

Comment by Graydon Hoare (JIRA)

Also worth noting in this case a workaround is to access super.a rather than self.a.

Would that call the `didSet` of an overridden `a: Int`?

Comment by Graydon Hoare (JIRA)

Not sure I understand; if you override the instance property a:Int in the subclass (i.e. with a computed property) there's no shadowing, the access resolves to the override. The only bug here (which I agree, may well be a bug) is when the static property of the subclass incorrectly shadows a non-overridden instance property of the superclass.

Am I misunderstanding the question?