Replies: 2 comments 2 replies
-
Sometimes correct code can take too much time to compile. You can add type annotations to help the compiler, because this happens in a view builder and you want to avoir explicit types you can have the same result by splitting you view into smaller ones.
or
Using private computed properties is convenient as you get access to the view properties including the store and environment easily. Now, you will often see that you get this warning on invalid code and after splitting the compiler will be able to find the issue before it times out and show it to you. |
Beta Was this translation helpful? Give feedback.
-
Thank you @Alex293, Also assuming that my additions to PointFree's example code are not the reason for compiler problems I'll create an issue from this discussion. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I started to convert an app to the prerelease/1.0 branch using stack-based and tree-based navigation. Some features use multiple destinations, e.g. one alert and four fullScreenCover. Unfortunately Xcode gives me the 'The compiler is unable to type-check this expression in reasonable time' error on the view's body. I can get rid of the error by commenting a few fullScreenCover modifiers, but Xcode gives no hint on the underlying problem. I'm using Xcode 14.3.1 and the latest TCA prerelease/1.0 commit/b2815ca
The problem seems to be not related to my app because I modified PointFree's Standups example slightly (added dummy destinations, added a menu to the toolbar...) and the error showed up:
Has anybody noticed this problem? Any help would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions