<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="">Well, here is what I got in IBM Swift Sandbox. <a href="http://swift.sandbox.bluemix.net/#/repl/5913a8594ee0cd258050b2fd" class="">http://swift.sandbox.bluemix.net/#/repl/5913a8594ee0cd258050b2fd</a></div><div class="">If I got you right, it works.</div><div class=""><br class=""></div><div class="">Yes, partially implemented functions is a problem. But we definitely could mark the ones that are not implemented at all and not being called.</div><br class=""><div><blockquote type="cite" class=""><div class="">On 11 May 2017, at 02:43, Philippe Hausler <<a href="mailto:phausler@apple.com" class="">phausler@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">This of course is predicated upon availability macros working appropriately on linux (which last time I checked we don’t have a version variant). It is definitely worth investigation.<br class=""><br class=""><blockquote type="cite" class="">On May 10, 2017, at 16:41, Tony Parker via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a>> wrote:<br class=""><br class="">Hi Sergej,<br class=""><br class="">This is a good idea, but there are some additional things to consider. In some cases, methods are partially unimplemented (with edge cases, or at least less common cases remaining unfinished). The availability macro can’t reflect that status.<br class=""><br class="">In other cases, we want to partially implement one function but still call through to an unimplemented function. The entire call may fail with the assert, but at least we have part of the implementation in place.<br class=""><br class="">- Tony<br class=""><br class=""><blockquote type="cite" class="">On May 10, 2017, at 4:01 PM, Sergej Jaskiewicz via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a>> wrote:<br class=""><br class="">I was wondering why cannot we just mark all the methods/properties/functions in Swift Foundation that are NSUnimplemented or call a subroutine that is NSUnimplemented like this:<br class=""><br class="">@available(*, unavailable, message: “foo is not implemented yet”)<br class="">func foo() { NSUnimplemented() }<br class=""><br class="">In this case we can be sure at compile time that we don’t use code that will definitely crash.<br class="">_______________________________________________<br class="">swift-corelibs-dev mailing list<br class=""><a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev<br class=""></blockquote><br class="">_______________________________________________<br class="">swift-corelibs-dev mailing list<br class=""><a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev<br class=""></blockquote><br class=""></div></div></blockquote></div><br class=""></body></html>