[swift-evolution] [Proposal Draft] Literal Syntax Protocols

[Erica Sadun]

> On Jun 28, 2016, at 7:52 PM, Matthew Johnson <matthew at anandabits.com> wrote:
> 
>> 
>> On Jun 28, 2016, at 8:35 PM, Erica Sadun via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> 
>> 
>>> On Jun 28, 2016, at 6:13 PM, Dave Abrahams <dabrahams at apple.com <mailto:dabrahams at apple.com>> wrote:
>>>> Or we're clueless AND it's a bad name.
>>> 
>>> It's possible, but until we have an objective rationale for why it's bad
>>> (arguments that it seems to imply what turns out to be the actual
>>> meaning of the protocol don't count!), *and* a better alternative, it's
>>> sort of moot.  If you don't like `Syntax.IntegerLiteral` or
>>> `Syntax.IntegerLiteralExpressible` then I'm out of suggestions.
>>> 
>>>> func f<T: IntegerPromotion>() -> T {
>>>>    return 42 // the answer to everything
>>>> }
>>> 
>>> Promotion means something very different; something that we actually
>>> expect to incorporate into the language one day.
>> 
>> Syntax.MarvinTheDepressedIntegerLiteral
> You really have me laughing with some of these!  Thanks Erica. :)

A few more, with a slightly different approach that pushes the literal part towards the end of the name:
Syntax.SupportsIntegerLiterals
Syntax.AcceptsIntegerLiterals
Syntax.IncludesIntegerLiterals
Syntax.IncorporatesIntegerLiterals

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160628/d870da39/attachment.html>