I've opened a few jira tickets:
- https://bugs.swift.org/browse/SR-2901 for this bug (has some numbers on
the impact in our project)
- https://bugs.swift.org/browse/SR-2902 for adding the expression type
checker timer, since it's looking like I won't have time to get to in the
next 2 weeks
I've
Okay great I'll open one soon! And just to clarify, that 2521 number is
counting the generated setters and getters (there are fewer number of
actual lines of "let" and "var" property code).
In the main target, there are 607 .swift files (guess we can deduce that
those properties are parsed once
> On Oct 7, 2016, at 2:35 PM, Ben Asher wrote:
>
> Hello again! I wanted to follow up with some more numbers and feedback. I
> wasn't able to easily compile a single file from our project from the CLI. I
> started putting together a command with all of the necessary
Hello again! I wanted to follow up with some more numbers and feedback. I
wasn't able to easily compile a single file from our project from the CLI.
I started putting together a command with all of the necessary framework
includes, flags, etc., but I moved on because it was taking awhile,
becoming
> On Oct 5, 2016, at 3:37 PM, Ben Asher wrote:
>
> I just tried with both Xcode 8.1 beta 2 and Xcode 8.0, and 8.1b2 seems maybe
> 15s faster (to build our main huge target): 7m28s compared to 7m43s. It's
> some improvement, but I'm not exactly sure what kind of
I just tried with both Xcode 8.1 beta 2 and Xcode 8.0, and 8.1b2 seems
maybe 15s faster (to build our main huge target): 7m28s compared to 7m43s.
It's some improvement, but I'm not exactly sure what kind of improvement
was expected.
Is there any profiling/tracing you all would recommend to help
I didn't know about that warning, so thanks for sharing that! Having this
enabled will help somewhat, at least in terms of keeping specific
slow-to-compile functions out of our master branch.
That said, I understand Jordan's response (in SR-2741) of being "leery of
'productizing'" these flags.
> On Oct 4, 2016, at 2:38 PM, Ben Asher via swift-dev
> wrote:
>
> Hello! I work with a large project (~900 .swift files and more .m files). We
> have a nightly job that compiles the app and calls out function bodies (using
> -debug-time-function-bodies) that are slower
Hi Ben,
I'd really like to see improvements here as well. I don't know what reports
would be useful to the Swift team, but allow me to point out
https://github.com/apple/swift/commit/18c75928639acf0ccf0e1fb6729eea75bc09cbd5,
which adds a -warn-long-function-bodies option that you may be able to
Hello! I work with a large project (~900 .swift files and more .m files).
We have a nightly job that compiles the app and calls out function bodies
(using -debug-time-function-bodies) that are slower than 100ms to compile.
Since upgrading to Swift 3, the number of trouble function bodies has one
10 matches
Mail list logo