Agreed. I'm not convinced that this actually prevents any more errors than
it might cause (forgot to finish writing my "repeat" block, and now my app
is unresponsive), and I don't think there's enough of an expressivity win
to add another keyword.

Austin

On Tue, May 10, 2016 at 1:04 PM, Haravikk via swift-evolution <
[email protected]> wrote:

>
> On 10 May 2016, at 08:27, Nicholas Maccharoli via swift-evolution <
> [email protected]> wrote:
>
> But I think it might be best to change the syntax / behaviour of `repeat`
> to loop
> indefinitely if no trailing while clause is present:
>
>     repeat {
>         if ... { break }
>         //...
>     }
>
>
> -1 from me on both counts; the thing I like about while true is that it’s
> explicit about what I meant, whereas a repeat block with no while clause is
> indistinguishable from me forgetting to include one, or me wanting an
> infinite loop.
>
> An alternative could be to add a new “forever” keyword or something
> similar, replacing while true wherever applicable, but personally I don’t
> think it’s that important.
>
> _______________________________________________
> swift-evolution mailing list
> [email protected]
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to