<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Understood. I had presumed designing a proper interface for Swift to provide that information out as a part of the higher level feature (although I guess I didn't make that clear in the bug).<div class=""><br class=""></div><div class=""> - Daniel</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 25, 2016, at 11:41 AM, Jordan Rose <<a href="mailto:jordan_rose@apple.com" class="">jordan_rose@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I commented in the bug, but I'll reply here too: this was a debugging tool added for us, and isn't really ready for the average Swift user. In particular:</div><div class=""><br class=""></div><div class="">- It does a pretty lousy job of identifying functions without names</div><div class="">- It doesn't include type-checking of expressions <i class="">not</i> in function bodies, like initial values for properties</div><div class="">- It only has a (very basic, unsorted) human-readable output form, instead of something properly tabular</div><div class="">- It can only dump to stderr</div><div class="">- It's only function-granular, not statement-granular</div><div class="">- It only includes statement/expression type-checking (though admittedly that's the part of the compiler most likely to have runaway growth)</div><div class="">- It doesn't provide any guidance on how to make things better</div><div class=""><br class=""></div><div class="">I'd rather not commit to providing this feature "publicly" until these problems are at least addressed, if not fixed.</div><div class=""><br class=""></div><div class="">(I'm fine with letting people know about the debug option. I just don't want to consider it an official, supported feature of Swift.)</div><div class=""><br class=""></div><div class="">Jordan</div><div class=""><br class=""></div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jan 23, 2016, at 20:21, Daniel Dunbar via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">It occurs to me that we should just get SwiftPM to have a feature to aggregate and report that data automatically:<br class=""> <a href="https://bugs.swift.org/browse/SR-608" class="">https://bugs.swift.org/browse/SR-608</a><br class=""><br class="">This would be a decent package manager starter bug, I'm guessing it isn't all that much work.<br class=""><br class=""> - Daniel<br class=""><br class=""><blockquote type="cite" class="">On Jan 23, 2016, at 4:03 PM, Joe Groff <<a href="mailto:jgroff@apple.com" class="">jgroff@apple.com</a>> wrote:<br class=""><br class=""><br class=""><blockquote type="cite" class="">On Jan 23, 2016, at 3:56 PM, David Turnbull via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:<br class=""><br class="">I get the impression that there's no immediate solution. Will Swift 3.0 improve build times?<br class=""></blockquote><br class="">We hope so. Joe Pamer just landed some improvements into the master branch that should improve a lot of common cases, and I believe more improvements are on the way. In the meantime, Bryan Irace recently wrote an article that might help, about using some of the compiler's internal debugging flags to find and improve problem points: <a href="http://irace.me/swift-profiling/" class="">http://irace.me/swift-profiling/</a><br class=""><br class="">-Joe<br class=""><br class=""></blockquote><br class="">_______________________________________________<br class="">swift-users mailing list<br class=""><a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-users" class="">https://lists.swift.org/mailman/listinfo/swift-users</a><br class=""></div></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></div></body></html>