[swift-evolution] Analysis of case conventions for initialisms

[Matthew Judge]

I had the same initial reaction as Dave to Jessy's suggestions, however,
the idea does kind of make sense. I'm not saying I like it, but it doesn't
bother me nearly as much as I thought it would. (I think the rule Jessy was
using would be the following.)

func hTMLDigest(for hTML: String) -> HTMLDigest

> If an initialism is used, treat each letter as its own word.


On Fri, Feb 12, 2016 at 1:34 AM, Dave Abrahams via swift-evolution <
swift-evolution at swift.org> wrote:

>
> on Thu Feb 11 2016, Jessy Catterwaul <swift-evolution at swift.org> wrote:
>
> > It is too complicated to have different rules when an initialism is used,
> > or not.
>
> I take it you'd be in favor of option 2 on that page, then?
>
> > uniformResourceLocatorForPublication
> > uRLForPublication
>
> I don't understand what that example is supposed to show.  No convention
> ever suggested “uRL”, and I can't imagine anyone writing that.  Can you?
>
> > Sent from my iPad
> >
> > On Feb 12, 2016, at 12:51 AM, Dave Abrahams via swift-evolution <
> > 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.
> >
> > Cheers,
>
> --
> -Dave
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160212/589eac4b/attachment.html>