> On Aug 29, 2015, at 4:55 PM, Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > I think you can assume that the error message is in effect a secondary error. > The expression complexity isn’t the issue, but rather the (internal) path > Swift follows to compile it.
.. that seems very wise. I keep getting caught by the fact that Swift’s binding is much later than I’m used to .. even “+” need interpretation! > .. so it’s probably hitting some internal limit that seems otherwise > reasonable John Randolph mentioned he can evaluate my failing expression so I went off-list briefly with him to give him my actual playground. What fails with my Xcode 7 beta 6 worked with his beta 5. Quincey Morris suggests some limit is being exceeded and so it may be that John’s Mac is faster than mine and solves the complexity fast enough to escape a compiler timeout? This expression does spin up the fans on my laptop! Anyway, there’s not much to be done except: > but I don’t see there’s much you can do about it except to break up the > expression, until the compiler is fixed/improved. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
