[swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.
Chris Lattner
clattner at apple.com
Wed Dec 9 16:56:34 CST 2015
- Previous message: [swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.
- Next message: [swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
> On Dec 9, 2015, at 1:26 PM, Amir Michail via swift-evolution <swift-evolution at swift.org> wrote:
>
> With such constructs, you could avoid using labels most of the time.
Quick comment: this doesn’t eliminate the need for labels (since they provide the ability to break out of e.g. doubly nested for loops), but it does add complexity to the language. As such, it doesn’t seem like a clear win to me.
-Chris
>
> For example:
>
> for … {
> if … {
> guard … else { break if }
> ...
> }
> }
>
> for … {
> for … {
> if … {
> break outer for
> }
> }
> }
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
- Previous message: [swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.
- Next message: [swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the swift-evolution
mailing list