[swift-evolution] Proposal: 'T(literal)' should construct T using the appropriate literal protocol if possible
matthew at anandabits.com
Fri Jun 3 19:13:08 CDT 2016
Sent from my iPad
On Jun 3, 2016, at 6:23 PM, John McCall <rjmccall at apple.com> wrote:
>>> On Jun 3, 2016, at 4:07 PM, David Sweeris <davesweeris at mac.com> wrote:
>>> On Jun 3, 2016, at 16:17, Matthew Johnson via swift-evolution <swift-evolution at swift.org> wrote:
>>> Using an external parameter label in a declaration and allowing it to be omitted at the call site does not feel like the right answer to me. I think we can find a better way to present this syntactically.
>> +eleventy gajillion
> I'm actually quite happy with the user-facing aspects of the current literal protocols and see zero reason to update them for this, so if that's the choice, I'll just leave this aside.
Are you suggesting that preserving the current syntax of the literal protocols is more important than fixing this behavior so it works like most people seem to expect? Why not be open to other syntactic solutions?
More information about the swift-evolution