Maybe file a bug to see if it's expected.
But at first glance it seems clear to be ambiguous scope. it can't figure out
that the first {} is part of the condition rather than the thing triggered by
the condition.
A do while knows more easily because the {} after do is what is conditionally
executed.
Honestly it starts to look Perly with that much crammed in either way.
Sent from my iPhone
> On Aug 19, 2015, at 3:04 PM, Antonio Nunes <[email protected]> wrote:
>
> In Swift 2.0 I can write this:
>
> repeat {
> …
> } while reminder.exclusions.filter { $0.spansTime(t) }.count > 0
>
> but I can’t write this:
>
> if reminder.exclusions.filter { $0.spansTime(t) }.count > 0 {
> …
> }
>
> which gives an error about consecutive statements on a line needing a “;”
>
> If have to write this:
>
> if (reminder.exclusions.filter { $0.spansTime(t) }.count > 0) {
> …
> }
>
>
> Any ideas why?
>
> -António
> _______________________________________________
>
> 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/dangerwillrobinsondanger%40gmail.com
>
> This email sent to [email protected]
_______________________________________________
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]
