<html><head></head><body>+1 But your example is too good to be true. :)<div><br></div><div>What would happen to this code:</div><div><br></div><div>class A { </div><div><br></div><div> var value: Type? = nil</div><div><br></div><div> func reset() { self.value = nil }</div><div><br></div><div> func test() {</div><div><br></div><div> self.value = self.value ?? Type()</div><div><br></div><div> self.reset()</div><div><br></div><div> self.value.doSomething() </div><div><br></div><div> // can the compiler be sure that our value wasn't reset somewhere from a different scope ?</div><div> }</div><div>}</div><div><br></div><div>I'm curious what will happen here. Can someone clarify on that?</div><div> <br><div class="bloop_sign"><div>-- <br>Adrian Zubarev</div></div> <p class="gmail_quote" style="color:#000;">Am 29. April 2016 um 16:37:37, Tod Cunningham via swift-evolution (<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>) schrieb:</p> <blockquote type="cite" class="gmail_quote"><span><div><div></div><div>I'm new to the swift evolution community, but I wanted to toss an idea out there to get some feedback on it. So here it goes...
<br>
<br>Currently, if you assign a non-nil value to an optional and then want to access that optional later, in the same context, you need to manually unwrap the value. This is usually done either by using "!" or by using something like "if let" or guard.
<br>
<br>What would it be like if the compiler could auto unwrap, in cases where in knows the optional will have some value? This would make the code "clean" and still be safe.
<br>
<br>This concept of Auto Unwrapping of Optionals is similar to Implicitly Unwrapped Optionals, but is only applied when the compiler knows it is safe to do so.
<br>
<br>Take the following example:
<br>
<br>class Test {
<br> var today: NSDate? = nil
<br> func test() {
<br> today = today ?? NSDate()
<br> print("Today is \(today)") // Would be printed as an optional
<br> let timeInterval: NSTimeInterval = today!.timeIntervalSinceNow // Requires ! or (if let) to unwrap
<br> // ... do stuff with timeInterval ...
<br> }
<br>}
<br>
<br>With the above example, the compiler could known that today has a value after it's set in the test method. So why couldn't the compiler auto unwrap it when accessed? This would mean manual unwrapping would be unnecessary:
<br>
<br>class Test {
<br> var today: NSDate? = nil
<br> func test() {
<br> today = today ?? NSDate()
<br> print("Today is \(today)") // Would be printed as a value (not an optional)
<br> let timeInterval: NSTimeInterval = today.timeIntervalSinceNow // No ! required (auto unwrapped)
<br> // ... do stuff with timeInterval ...
<br> }
<br>}
<br>
<br>If the value later gets set to an optional value, then it will no longer be auto unwrapable :
<br>
<br>class Test {
<br> var today: NSDate? = nil
<br>
<br> func optionalDay() -> NSDate? {
<br> return NSDate()
<br> }
<br>
<br> func test() {
<br> today = today ?? NSDate()
<br> print("Today is \(today)") // Would be printed as a value (not an optional)
<br> let timeInterval: NSTimeInterval = today.timeIntervalSinceNow // No ! required (auto unwrapped)
<br> let timeInterval2: NSTimeInterval = today!.timeIntervalSinceNow // Explicit unwrapping would still be allowed
<br>
<br> // If today is assigned an optional value, we can no longer auto unwrap it
<br> today = optionalDay()
<br> print("Today is \(today)") // Would be printed as an optional
<br> let timeInterval3: NSTimeInterval = today!.timeIntervalSinceNow // manual unwrapping would be required
<br> }
<br>}
<br>
<br>Note in the above example, explicit unwrapping would still be allow. The variable is still an optional. This allows for existing code to remain unchanged.
<br>
<br>This change would encourage less use of forced unwrapping "!", generally require the developer to write less code, and would maintain code safety. On the down side, it is performing some compiler “magic”. It would be yet another thing to explain when trying to introduce people to swift and especially optionals.
<br>
<br>What do you all think, would something like this be worth pursuing, what other pluses or minus would this introduce, has something like this already been discussed?
<br>
<br>Thanks,
<br>Tod Cunningham
<br>
<br>_______________________________________________<br>swift-evolution mailing list<br>swift-evolution@swift.org<br>https://lists.swift.org/mailman/listinfo/swift-evolution<br></div></div></span></blockquote>
</div></body></html>