Investigate backporting Swift 5 compiler behavior to Swift 4.2 and earlier

gradle / gradle-native

The home of Gradle's support for natively compiled languages

https://blog.gradle.org/introducing-the-new-cpp-plugins

Apache License 2.0

91 stars 8 forks source link

Investigate backporting Swift 5 compiler behavior to Swift 4.2 and earlier #1004

Open lacasseio opened 5 years ago

lacasseio commented 5 years ago

Swift 5 compiler is a bit more smart in what files it modified on disk. In fact, this integration test doesn't recompile anything as the removed file is unrelated to any of the other source files. When renaming a file, only the renamed file is compiled. We have .d files that describe how the files are related to one and another. There is a chance we could shortcircuit the incremental compilation and avoid certain files to be compiled on Swift 4.2 and earlier.

lacasseio commented 4 years ago

For some reason, it seems this optimization was broken on Swift 5.1.