Proposal: Swift should automatically modify your code to improve compile times


(Amir Michail) #1

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.


(Chris Lattner) #2

I respectfully disagree. The Swift compiler should just not require you to change your code in order for it to compile fast. We’re working on it.

-Chris

···

On Mar 5, 2016, at 5:23 AM, Amir Michail via swift-evolution <swift-evolution@swift.org> wrote:

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.


(James Campbell) #3

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 :wink:

···

Sent from Supmenow.com

On Sat, Mar 5, 2016 at 5:24 AM -0800, "Amir Michail via swift-evolution" <swift-evolution@swift.org> wrote:

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


(Amir Michail) #4

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 :wink:

Yes it can up to a certain limit like 30 seconds.

···

On Mar 5, 2016, at 8:25 AM, James Campbell <james@supmenow.com> wrote:

Sent from Supmenow.com <http://supmenow.com/>

On Sat, Mar 5, 2016 at 5:24 AM -0800, "Amir Michail via swift-evolution" <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote:

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


(Amir Michail) #5

I thought this type inference is exponential in the worst case.

···

On Mar 5, 2016, at 12:14 PM, Chris Lattner <clattner@apple.com> wrote:

On Mar 5, 2016, at 5:23 AM, Amir Michail via swift-evolution <swift-evolution@swift.org> wrote:

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.

I respectfully disagree. The Swift compiler should just not require you to change your code in order for it to compile fast. We’re working on it.

-Chris