<html><head></head><body><div>These should be fix its but the problem is the compiler needs to be able to compile it in order to know what needs fixing but it can't do that if it took time to compile ;)<br><br><div class="acompli_signature">Sent from <a dir="ltr" href="http://supmenow.com" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="0">Supmenow.com</a></div><br></div><br><br><br>
<div class="gmail_quote">On Sat, Mar 5, 2016 at 5:24 AM -0800, "Amir Michail via swift-evolution" <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="3D"ltr"">
<pre>I think it’s too much to require Swift developers not just to profile their code to improve running times but also to profile the compilation of their code to reduce compile times.
Swift should automatically identify expressions that took too long to compile and automatically insert type annotations in the source code to speed up future compiles of those expressions.
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
</pre>
</div>
</blockquote>
</div>
</body></html>