![]() You can rename all of your types and methods in order to preserve any secrets you don't want to share.Īs a general rule, the type-checking time of an individual function is not affected by things like other function bodies (you can replace them all with empty bodies or preconditionFailure), and it shouldn't be affected by obviously uninvolved declarations (if the function never uses the name foo, you should be able to drop any declarations like func foo()), but it can definitely be affected by declarations with the same name that aren't supposed to be used (like overloads that don't match the types involved). If there are, try to copy those functions into new projects with just as much context as is necessary to keep them slow to compile, then file bugs with those reduced examples. Assuming it shows that the problem is indeed the Swift compiler, rebuild using the long-compile-time warnings and compare the output to see if there are functions that are significantly slower to type-check than they used to be. The first thing to do is to get build timings under both releases so that you can verify that the problem is that Swift compilation is slower and it's not something more surprising in the build. ![]() This blog post seems to be a pretty complete and up-to-date exploration of how to approach this. ![]() In particular, you may be able to isolate some code that's now significantly slower to build. I understand that you can't share all of your code, but there are still things you can do that can potentially let us fix your problem. We're always interested in improving build times.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |