[swift-evolution] Rename 'guard' to 'ensure'

[Shawn Erickson]

We need a guard emoji... how about calling it🛂?

;)
On Mon, Feb 22, 2016 at 9:25 AM Erica Sadun <erica at ericasadun.com> wrote:

> > " a vision of a little guard standing at his guard post checking papers"
>
> Raises hand. Me too. I like my little guard.
>
> On the other hand, I'd love if assert/precondition would be combined into
> a single call, with an optional `forReleaseBuild:` arg (better named) that
> defaults to false.
>
>
> -- E
>
> On Feb 22, 2016, at 10:07 AM, Shawn Erickson via swift-evolution <
> swift-evolution at swift.org> wrote:
>
> Ensure(TM) ...has a little much sugar for my wants in a drink
>
> I get and like the suggestion from a grammar pov however guard is a little
> more forceful in terminology which aligns with the fact that you cannot
> proceed past the guard unless the condition is met. (I have a vision of a
> little guard standing at his guard post checking papers)
>
> -Shawn
>
> On Mon, Feb 22, 2016 at 9:01 AM John Flanagan via swift-evolution <
> swift-evolution at swift.org> wrote:
>
>> The functionality of ‘guard’ is great and this proposal has nothing to do
>> with changing that. The only suggestion is that the word ‘ensure’ would
>> better communicate what a ‘guard’ statement does to those encountering it
>> for the first time and would make code more readable in general.
>>
>> Example:
>>
>> ensure foo != nil else {
>>    return;
>> }
>>
>> -John
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160222/461811de/attachment.html>