<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi David,<div><br></div><div>I think it is a bit too early to start using Swift in WebKit, especially since the language is still evolving. Eventually, I think we should start using it, but I’d like for it to settle a bit before we do.</div><div><br></div><div>- Sam</div><div><br></div><div><br><div><div>On Jul 28, 2014, at 12:47 PM, David Farler <<a href="mailto:dfarler@apple.com">dfarler@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hello all,<div class=""><br class=""></div><div class="">I have the following bug to help build out support for layout tests in the iOS Simulator.</div><div class=""><br class=""></div><div class="">iOS Simulator LayoutTestRelay</div><div class=""><a href="https://bugs.webkit.org/show_bug.cgi?id=135269" class="">https://bugs.webkit.org/show_bug.cgi?id=135269</a></div><div class=""><br class=""></div><div class="">I'd like to include this as a new tool written in Swift.</div><div class=""><br class=""></div><div class="">Why I think it's fine in this case:</div><div class="">- This tool is specific to the iOS and OS X platforms</div><div class="">- Swift is a fully supported, albeit new, language starting in Xcode 6.</div><div class="">- Swift is probably the best way to get Objective-C bridging "for free" in the long term</div><div class="">- Swift supports script-like "immediate mode" with good JIT-compiled performance</div><div class=""><div class="">- The tool's size and scope is sufficiently small with no complex or WebKit-specific dependencies</div></div><div class=""><br class=""></div><div class="">I understand that its freshness and continual evolution means that we won't reviewer support relative to our C family languages. I would argue that it will be difficult to subjectively tell when the time is "right", that a good way to solve that is to start using the language itself, and take an incremental approach to crafting the Swift story in WebKit. Using it for some simple tools is a good place to start.</div><div class=""><br class=""></div><div class="">The larger discussion of using Swift in larger AOT-compiled contexts but is probably going to happen in this thread anyway, so let's have it:</div><div class=""><br class=""></div><div class=""><b class="">What of future use of Swift in WebKit?</b></div><div class=""><br class=""></div><div class="">Regards,</div><div class="">David Farler</div></div>_______________________________________________<br>webkit-dev mailing list<br><a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>https://lists.webkit.org/mailman/listinfo/webkit-dev<br></blockquote></div><br></div></body></html>