[swift-evolution] Analysis of case conventions for initialisms

Craig Cruden ccruden at novafore.com
Fri Feb 12 17:45:43 CST 2016

I picked #2 (based on your example) but I was fine with either #1 or #2 (could have even waffled back and forth depending on the day)… so #1 would make me happy.

Did not really like #3.

And if I am happy, everyone should be happy :p

> On 2016-02-13, at 6:31:34, Dave Abrahams via swift-evolution <swift-evolution at swift.org> wrote:
> on Thu Feb 11 2016, Dave Abrahams <swift-evolution at swift.org> wrote:
>> I just posted a write-up about various case conventions for initialisms:
>> https://gist.github.com/dabrahams/55fc5ece355da4664730.  I was surprised
>> at how it turned out, FWIW.
> FYI, it looks like the API guidelines working group has settled on
> convention #1, which is what the standard library currently does.
> Coincidentally, this seems to have resulted in the fewest number of
> strong objections in an area where strong opinions abound (except for
> Trent—sorry, Trent).
> -- 
> -Dave
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list