> On Jul 11, 2016, at 19:13, Jacob Bandes-Storch via swift-evolution
> <[email protected]> wrote:
>
> I'd be happy with a warning + fix-it too.
>
>> On Mon, Jul 11, 2016 at 5:05 PM, Xiaodi Wu <[email protected]> wrote:
>> Maybe just a warning + fix-it would be sufficient?
>>
>>> On Mon, Jul 11, 2016 at 19:02 Jacob Bandes-Storch via swift-evolution
>>> <[email protected]> wrote:
>>> Tangential: Is there any way to make it impossible to call these
>>> literal-initializers explicitly, instead requiring "<literal> as T" or just
>>> "<literal>" in a typed context?
>>>
>>> I have seen several explicit calls of these initializers where literals
>>> would have been more appropriate, such as "Set(arrayLiteral: foo, bar)",
>>> and I think this only happens because folks find these initializers via
>>> code completion. I can't think of any reason why you'd want to invoke one
>>> by name rather than by using a literal.
I don't see how this is a problem.
- Dave Sweeris
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
