is duplicated by:

• SR-4395 Incomplete initialization of self results in confusing error messages with @autoclosure functions
• SR-7584 Seemingly incorrect "Constant 'self.X' captured before being initialized" compiler error in struct initializer
• SR-7990 Using && on instance property in initializer results in confusing/incorrect error message
• SR-11493 Can't use property of self before initialization when using the && operator

Issue Description:

When checking a conditional for an if statement in a initializer, specifying a member variable in the second or subsequent component will cause the compiler to complain that self was captured by a closure before all members were initialized.

The following code snippet demonstrates the problem:

class A {
    var a: Int?
    var b: Int
    init() {
        a = 4
        var c: String?
        if c == nil && a == nil {
            print("in")
        }
        b = 4
    }
}

Interestingly, switching the ordering of the c and a nil checks will cause the error to go away.

I created a snapshot of the issue in the IBM Sandbox: http://swiftlang.ng.bluemix.net/#/repl/fc77261825ff05d35c3b3dbde1259ed9c9c0366688b3dc1f87216ba6ec4e75ae