Attachment: Download

duplicates:

• SR-4387 Compiler Segmentation Fault 11 on wrongly ordered lets

Issue Description:

With the following code sample, the Swift compiler will seg fault.

The intention of the sample is poorly reasoned; occluding a instance field with a locally unwrapped optional of a different type, I suspect, is not "good practice". That said, I suspect/ expect that the compiler should allow it to be defined as that new type in scope - to disambiguate the two by dereferencing `self` for the instance field.

class Foo {
  var a: String? = nil
  func makeBar() -> Bar? {
    guard let aString = a,
    let a = Int(aString) else { return nil }
    return Bar(b: a)
  }
}

class Bar {
  let b: Int
  init(b: Int) {
    self.b = b
  }
}

{{ }}