>> Improving incremental mode
>> ==
>>
>> Another area that could use work is the incremental compilation logic in the
>> driver -- that is, reducing the number of times a file is rebuilt when it
>> "doesn't need to be" -- and some of the documentation and driver-level
>
> On Nov 12, 2017, at 8:30 AM, Brian Gesiak via swift-dev
> wrote:
>
> Hello all!
>
> I'm looking for a body of work to do on the Swift compiler for an upcoming
> programmer retreat I'm attending in January [1]. I've read a lot of blog
> posts with tips for diagnosing slow Swift compile tim
Hi,
This is just an update on some work that's been ongoing in the past several
months related to tracking and improving Swift compilation performance. I've
been helping coordinate some of that work: documenting what's known about
compilation performance patterns and diagnostic machinery, incre
> On Jan 26, 2017, at 2:07 AM, Andrew Trick via swift-dev
> wrote:
>
> Before I pull in a large PR that "accidentally" reformats a bunch of code, I
> want to get feedback on how Swift compiler devs plan to use `clang-format`.
> (BTW, here's the PR https://github.com/apple/swift/pull/6922).
>
sed by my generics refactoring. Looks like Graydon
> reverted it already. Sorry for the inconvenience y’all!
>
> Slava
>
>> On Nov 22, 2016, at 12:46 PM, Graydon Hoare via swift-dev
>> mailto:swift-dev@swift.org>> wrote:
>>
>> Yes, that configuration has bee
Yes, that configuration has been failing LLDB tests for a few days; it's being
looked into. Unfortunately many people are on vacation this week, but I'll try
to revert whatever's necessary soon. Will follow up here when fixed. Apologies
for the holdup.
-Graydon
> On Nov 21, 2016, at 10:41 PM,
Hi,
I've been working a bit on testing infrastructure for systematically improving
swiftc compilation performance. Attached is a document summarizing both the
machinery I put together, and an example (small) bug recently fixed, as a case
study showing how to use it.
I'd like to encourage folks
If you can collect an instruments profile of the frontend running one of the
particularly-slow files, it might help localize the subsystem of the
typechecker; aside from that, I'm currently putting some new counters and
timers in the frontend, so am likely to have slightly more-constructive news
> On Jul 29, 2016, at 5:20 PM, Jacob Bandes-Storch via swift-evolution
> wrote:
>
> I am curious whether the team has thoughts on how to organize the compiler
> codebase in such a way that new features can be added, and possibly
> source-breaking changes made, while still keeping the old func
