<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I’m pretty much a +1 by default to anything that avoids unexpected runtime errors =D</div><div class=""><br class=""></div><div class="">But yeah, I agree that Swift’s type inference shouldn’t result in types that we can’t trust, and that it’s better to force the developer to declare what they want/expect the type to be. Most occurrences of AnyObject are one of only a few possible types, and well-documented (otherwise you’d be unable to do anything with them), so while looking up the types you need to check for is an added step, I think it’s worth the extra safety, especially with so much useful code still written in Objective-C.</div><br class=""><div><blockquote type="cite" class=""><div class="">On 23 Mar 2016, at 01:59, Kevin Lundberg via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">In "Using Swift with Cocoa and Objective-C", this behavior is described as part of how AnyObject works:<div class=""><br class=""><div class=""><div class=""><i class="">“You can also call any Objective-C method and access any property without casting to a more specific class type." … "However, because the specific type of an object typed as AnyObject is not known until runtime, it is possible to inadvertently write unsafe code. As in Objective-C, if you invoke a method or access a property that does not exist on an AnyObject typed object, it is a runtime error.”</i></div><div class=""><br class=""></div><div class="">I propose that we remove this behavior entirely to push swift further in the direction of type safety.</div><div class=""><br class=""></div><div class=""><b class="">Rationale:</b></div><div class="">Even if you don’t mean to write code that relies on this behavior, it's easy to accidentally do so when interfacing with various Cocoa APIs due to type inference. A developer may not even realize that their code is unsafe since their code will compile just fine when calling obj-c visible methods. Removing this behavior would alleviate any confusion that a developer may have while writing this, especially as it is not a highly advertised feature of AnyObject. Furthermore, anyone who reads swift code using this will know with more certainty what types the author expects to be using here since an explicit cast will be required.</div><div class=""><br class=""></div><div class=""><b class="">Considerations:</b></div><div class="">If this is done, the way I see AnyObject behaving is similar to Any, where you need to manually downcast in order to call methods on things. Code would change from this:</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">class Foo: NSObject { func bar() {} }</div><div class=""><div class="">let things = NSOrderedSet(object: Foo())</div><div class=""><br class=""></div><div class="">for thing in things { // thing is AnyObject</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>thing.bar() // happens to work but not verified by compiler, may crash in the future</div><div class="">}</div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">to something like this:</div><div class=""><br class=""></div><div class="">//...</div><div class=""><br class=""></div><div class="">for thing in things {</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>if let foo = thing as? Foo { // needs an explicit cast</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>foo.bar() // type checked, verified by compiler, won’t crash due to missing method</div><div class=""> }</div><div class="">}</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">One ancillary benefit that I can see of doing this is that it could make AnyObject consistent across darwin and other platforms. As far as I can tell, this behavior only exists on platforms where swift integrates with the objective-c runtime, and doing this will help swift code be more portable as it doesn’t rely on this implicit behavior.</div><div class=""><br class=""></div><div class="">Any thoughts?</div><div class=""><br class=""></div><div class="">--<br class=""><div class="">
<div class="">Kevin Lundberg</div><div class=""><a href="mailto:kevin@klundberg.com" class="">kevin@klundberg.com</a></div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""></div></div></div></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>