Possible implementation strategy: Lazy variables are turned into computed properties during type checking in TypeCheckDecl.cpp's DeclChecker::visitBoundVariable method:

    // Synthesize accessors for lazy, all checking already been performed.
    if (VD->getAttrs().hasAttribute<LazyAttr>() && !VD->isStatic() &&
        !VD->getGetter()->hasBody())
      TC.completeLazyVarImplementation(VD);

    // If this is a willSet/didSet property, synthesize the getter and setter
    // decl.
    if (VD->hasObservers() && !VD->getGetter()->getBody())
      synthesizeObservingAccessors(VD, TC);

The lazy variable checking happens right before observers are normally synthesized. When we create the getter/setter for lazy variables inside TypeChecker::completeLazyVarImplementation, we should check for observers at that point and incorporate calls to the willSet/didSet methods in the lazy var's synthesized setter instead of calling synthesizeTrivialSetter. We should then suppress the error you get when observers are seen on a lazy property, since we know they're now taken care of as part of lazy property synthesis.

Comment by Jeff Johnson (JIRA)

Strangely, this pattern currently works

class Yep {
    lazy var foo:String = "Hi"
}
class Sub:Yep {
    override var foo:String {
        willSet {
            print("willSet")
        }
    }
}

even though this pattern doesn't:

class Nope {
    lazy var foo:String = "Hi" {
        willSet {
            print("willSet")
        }
    }
}

Comment by Ray Fix (JIRA)

A couple of us are looking at this at an try! Swift workshop in Japan this morning.

Comment by Mohit Athwani (JIRA)

Going to try working on this as my starter bug... Any tips from you guys?

Comment by Mohit Athwani (JIRA)

Is any body still working on this? Should I start looking into it?

PR here: #24043

This type checks now, but causes an issue with DI. I don't think it's a DI problem, I guess I messed up something in the type checker, so need to look into that.

@theblixguy, are you still working on this one?

(I'm checking in on all the StarterBugs that haven't been touched in over a month; it's totally fine if you just haven't had time but still want to keep it.)

I have a PR open (link above) - the only thing left to do is to figure out why DefiniteInitialization is complaining about the lazy property not being initialised when you add an observer. I’ll try to figure out today/tomorrow but I’m not very familiar with SIL so some help would be appreciated!

Hmm it seems like that DI issue is gone, but there's still an issue with SILGen. @slavapestov since you recently did some work on lazy properties, do you mind having a look at my PR? Thank you!

Decided to revisit this and I’ve now got it working: #31097

Fixed on master. @jckarter please verify using the next available snapshot!

@swift-ci create