Hi all,
In my continued investigation of Swift compile times I was able to gather
some interesting data.
In the last couple weeks we decided to put in a large dev effort to move
our entire codebase into frameworks. We'd been having really slow build
times (often 5 minutes for an incremental compi
On Mon, Apr 25, 2016 at 12:11 AM, Daniel Dunbar
wrote:
>
> On Apr 24, 2016, at 3:19 PM, Samantha John via swift-dev <
> swift-dev@swift.org> wrote:
>
> Hello List (cc/Jordan),
>
> At a high level: Brian and I are looking into contributing to incremental
> compila
y graph. I have no idea how optimized the bridging
>> functionality is but it has always seemed like a potentially weak part of
>> the dependency management. I imagine that with an objc half and a swift
>> half of the code base, every time you make a change in a swift file you
#x27;d love to hear
> from the core team to what extent this is true!
>
> George
>
>
>
> On Apr 7, 2016, at 5:35 PM, Samantha John via swift-dev <
> swift-dev@swift.org> wrote:
>
> Thank you Jordan! This is a great starting off point.
>
> I'm thinking about pro
ly, archive builds are always clean builds anyway.)
>
> There's a document in the Swift repo describing the logic behind Swift's
> dependency analysis:
> https://github.com/apple/swift/blob/master/docs/DependencyAnalysis.rst.
> The one thing that's *not* in there is the not
I have a large project (308 swift files, 441 objective c, 66k lines of
code) where incremental builds can be extremely slow. I'm trying to do some
profiling to figure out what type of things cause large scale recompiles.
The problem is that I can't find a good way of telling which files get
recompi
