Re: [swift-evolution] Guard let

Yes, this is the proper channel to discuss this kind of proposal. What you’re proposing has been brought up before, or as Chris Lattner put it: “Yes, this has thoroughly been beaten to death. It is also outside the scope of Swift 4 stage 1. That said, it is such a glaring problem that we’ll

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0176: Enforce Exclusive Access to Memory

> On 3 May 2017, at 22:06, John McCall via swift-evolution > wrote: > >> >> On May 3, 2017, at 3:56 PM, Florent Bruneau >> wrote: >> >> >>> Le 3 mai 2017 à 17:23, John McCall a écrit : >>> On May 3, 2017,

Re: [swift-evolution] [Pitch] Improve the API Design Guidelines about protocol naming

gt;> `Bounds`... >> >> Gwendal Roué >> >> >> Le 19 avr. 2017 à 23:35, Jordan Rose <jordan_r...@apple.com >> <mailto:jordan_r...@apple.com>> a écrit : >> >>> That was probably about the ObjC importer, which does this (appends >

Re: [swift-evolution] [Draft] Apply -ed/-ing rule to core functional methods (e.g. filter => filtered)

-0.5 I find the "term of art" argument strong in this case, especially for map/filter/reduce. These functions are different than for example `sort` because there can’t be a general mutating method of `map`. A variable of type `[A]` can’t be mutated to hold a `[B]` which would be the result of

[swift-evolution] [Draft] Lazy evaluation when assigning static variables

Several weeks ago I posted that I was confused by the differences between how static variables and lazy variables evaluated (or - as I would expect - didn’t evaluate) when initially assigned with a different value. It didn’t result in any discussion, but I encountered it again and decided to

Re: [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib

I would also be happy with ‘fold’/‘unfold’. The term of art argument applies to fold in the same way it does for ‘reduce’. Otherwise (if we stick with ‘reduce’) I find both ‘induce’ and ‘expand’ to be good names. I can also suggest ‘accumulate’. In each of these cases I prefer the local

Re: [swift-evolution] [Pitch] Tuple Destructuring in Parameter Lists

+1 I’ve tried to write parameter lists like `acc, (valueA, valueB) in` in the past, expecting it to work like this > On 05 May 2016, at 20:22, Dennis Weissmann via swift-evolution > wrote: > > Following a short discussion with positive feedback on >