Re: [swift-evolution] SE-0111 and Curried argument labels: Unintended Consequences

n <swift-evolution@swift.org > <mailto:swift-evolution@swift.org>> > Subject: [swift-evolution] SE-0111 and Curried argument labels: Unintended > Consequences > > SE-0111 established that Swift's type system would not allow function > argument labels to b

Re: [swift-evolution] SE-0111 and Curried argument labels: Unintended Consequences

@swift.org>> Subject: [swift-evolution] SE-0111 and Curried argument labels: Unintended Consequences SE-0111 established that Swift's type system would not allow function argument labels to be expressed as part of a function type. As I've been working with curried functions, I'm discov

Re: [swift-evolution] SE-0111 and Curried argument labels: Unintended Consequences

Thank you for that! -- E > On Oct 4, 2016, at 4:58 PM, Goffredo Marocchi wrote: > > Here is the message I was talking about: > https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160711/024331.html > >

Re: [swift-evolution] SE-0111 and Curried argument labels: Unintended Consequences

Here is the message I was talking about: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160711/024331.html Message quoted here for your convenience: > *Proposal: > https://github.com/apple/swift-evolution/blob/master/proposals/0111-remove-arg-label-type-significance.md > >

Re: [swift-evolution] SE-0111 and Curried argument labels: Unintended Consequences

I noticed this immediately and assumed that it was recognized as suboptimal but tolerable for now. The required underscores were meant to leave space for improvement in this regard, no? If not… sad face. TJ On Tue, Oct 4, 2016 at 12:21 PM, Erica Sadun via swift-evolution <

Re: [swift-evolution] SE-0111 and Curried argument labels: Unintended Consequences

I do not think the boat has sailed. I do remember this issue being actually revisited after initial approval because of the impact it had and quite a few members in this list, myself included, thought it was not helping readability and clarity and that it was strange this came after putting so

Re: [swift-evolution] SE-0111 and Curried argument labels: Unintended Consequences

> On Oct 4, 2016, at 9:32 AM, Michael Ilseman via swift-evolution > wrote: > >> >> On Oct 4, 2016, at 9:21 AM, Erica Sadun via swift-evolution >> > wrote: >> >> SE-0111 established that Swift's type

Re: [swift-evolution] SE-0111 and Curried argument labels: Unintended Consequences

> On Oct 4, 2016, at 9:21 AM, Erica Sadun via swift-evolution > wrote: > > SE-0111 established that Swift's type system would not allow function > argument labels to be expressed as part of a function type. As I've been > working with curried functions, I'm

[swift-evolution] SE-0111 and Curried argument labels: Unintended Consequences

SE-0111 established that Swift's type system would not allow function argument labels to be expressed as part of a function type. As I've been working with curried functions, I'm discovering an unintended consequence of this proposal in that it strips curried functions of their external labels