> On Jun 28, 2016, at 8:35 PM, Erica Sadun via swift-evolution > <[email protected]> wrote: > > >> On Jun 28, 2016, at 6:13 PM, Dave Abrahams <[email protected] >> <mailto:[email protected]>> 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. > > Next pitch: > Syntax.IntegerLiteralInsertion > Less successful attempts to brainstorm: > Syntax.IntegerLiteralAdvancement > Syntax.IntegerLiteralUpgrade > Syntax.FreelyIntegerReplaceable > Syntax.IntegerParkour > Syntax.TodayTheRoleOfTWillBePlayedByIntegerLiteral > Syntax.IntegerLiteralTypePoseur > Syntax.IntegerLiteral.Zigazigahh > Syntax.IntegerLiteralBoosterPack > Syntax.IntegerLevelUp > Syntax.IntegerElevator > Syntax.MarvinTheDepressedIntegerLiteral You really have me laughing with some of these! Thanks Erica. :)
> -- E > > > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
