> On 29 Apr 2016, at 15:37, Tod Cunningham via swift-evolution
> wrote:
>
> This concept of Auto Unwrapping of Optionals is similar to Implicitly
> Unwrapped Optionals, but is only applied when the compiler knows it is safe
> to do so.
>
> Take the following
> On 22 Apr 2016, at 23:43, Vladimir.S via swift-evolution
> wrote:
>
> 3. Disallow putting empty tuple () in parentheses
The thing is, Void is a typealias for ()
Therefore the impermissible:
(()) -> ()
Is identical to:
(Void) -> ()
So to follow these rules, it
A quick grep showed about 50 cases of using T1 -> T2 in my current project. Not
a huge amount, but not tiny either. It wouldn’t be a completely dreadful change
to make, just irritating having to add superfluous syntactical appendages to
pacify the computer.
> On 20 Apr 2016, at 00:28, Jacob
I’d place the ability to omit parenthesises for single args in the same
category as being able to omit `self` when accessing properties. They are small
conveniences that make a large difference to an entire codebase.
> On 19 Apr 2016, at 15:49, Erica Sadun via swift-evolution
>
Completely agree with Radek. I avoid unnecessary punctuation whenever possible,
which increases legibility IMHO; so this pernickety proposal makes me sad : (
> On 19 Apr 2016, at 08:46, Radosław Pietruszewski via swift-evolution
> wrote:
>
> Noo :(
>
> I
> I'm completely against replacing '->' by ':' it would make unreadable the
> declaration of a function taking a closure as parameter, or returning one
> (among other things).
>
> --
> Pierre
I agree with Pierre. Parameter names and functions as arguments or return
values are easily