<div dir="ltr">JIT is mentioned in [this thread](<a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/000983.html">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/000983.html</a>) and specifically by Chris Lattner in [this message](<a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001948.html">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001948.html</a>) and [this message](<a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/002135.html">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/002135.html</a>)<div><br></div><div><br></div><div>Long story short, a goal is not to leave much performance on the table for a JIT performance wise but the core team isn't against a JIT on principle.</div><div><br></div><div>TJ</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 28, 2015 at 6:47 PM, Joseph Bell via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Howdy,<div><br></div><div>Long time listener, first time poster. I've scanned through the last few weeks of posts to swift-evolution and didn't come across anything that appeared to address this, so I thought I would ask. If it has come up please let me know!</div><div><br></div><div>I'm sure most are familiar with building Python applications using __init__.py and organizing module code in subdirectories and then importing the code. Likewise, you can use a flat structure and have everything in a top-level namespace, importing class definitions with something along the lines of</div><div><br></div><div>from Foo import Foo</div><div>from Bar import Bar</div><div><br></div><div>f = Foo()</div><div>b = Bar()</div><div><br></div><div>Once this is executed there are Foo.pyc and Bar.pyc files littered in your directory.</div><div><br></div><div>Is there a plan for Swift to evolve into a language that can also perform JIT compilation/execution, in the same manner that running a single swift file (with no imports to local code) works today? Quite frankly I am looking forward to a day when I no longer have to deal with languages that define blocks through whitespace indentation.</div><div><br></div><div>Joe</div><div><br></div><div><br></div><div><br></div><div><br></div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=3FGfocPbgxkNkmje7djckg9Iw-2BGYY3X6RxJ1tkUXKCpYF7havLQxfPg9WizepUW8EFWaKwbzh4Wlx-2B-2BwtCH0RMcxmDakBjiZR-2FUduvLNGMzDK1bVH-2F3kPibANStRshYVryPDwd9enbn1j-2FcXKqTbZdCrDFUUms7FDYvnRCm7DxNpgHxJfS6odIOXvMgaaoemY68Ojh3VpRYNtYmGCqJvKnQDJUm2CoT0s8majRU6o-2F0-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important">
<br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div>