Clearly it’s a “more ambiguous” context than the while case, which prevents the compiler from realizing that there is an alternative analysis that works. In that case, it’s the error message that’s at fault, since it doesn’t really tell you what’s wrong. In fact, this “consecutive statements” error almost never gives any help, but I guess the compiler is reluctant just to admit it has no clue.
On Aug 18, 2015, at 23:04 , Antonio Nunes <[email protected]> wrote: > if (reminder.exclusions.filter { $0.spansTime(t) }.count > 0) { It might be clearer to write: > if reminder.exclusions.filter ({ $0.spansTime(t) }).count > 0 { _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
