Re: [swift-dev] Potential contributions to compilation time reporting?

> On Nov 28, 2017, at 5:01 PM, Mark Lacey via swift-dev > wrote: > > > >> On Nov 19, 2017, at 9:02 PM, Brian Gesiak via swift-dev > > wrote: >> >> Thanks for the reply, Graydon, and for your other email on the topic >>

Re: [swift-dev] Potential contributions to compilation time reporting?

> On Nov 19, 2017, at 9:02 PM, Brian Gesiak via swift-dev > wrote: > > Thanks for the reply, Graydon, and for your other email on the topic > ! > > I need to take more time to look into some of the things you menti

Re: [swift-dev] Potential contributions to compilation time reporting?

Thanks for the reply, Graydon, and for your other email on the topic ! I need to take more time to look into some of the things you mentioned, but I won't be able to do so in earnest for another few days. In the meantim

Re: [swift-dev] Potential contributions to compilation time reporting?

> 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

[swift-dev] Potential contributions to compilation time reporting?

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 times [2], and I was wondering if I could contribute to tooling in this area. (Just to m