[swift-evolution] Thoughts on replacing \() with $() or some other symbol

Joseph Bell joe at iachieved.it
Sun Jun 26 13:34:46 CDT 2016

Like others that have already responded, I would vote -1 to this proposal
based on evaluating the question "Is the problem being addressed
significant enough to warrant a change to Swift?"  My answer to that would
be no.  While it is indeed different from other languages there is no
relative difficulty in typing \( vs. any other sequence.

Thank you though for the time and thought put into writing up the
proposal.  It's this level of participation from the community and ability
to share thoughts and ideas in a public forum that has made open source
Swift so attractive to many.

On Tue, Jun 21, 2016 at 3:43 PM, Kenny Wyland via swift-evolution <
swift-evolution at swift.org> wrote:

> Hi all,
> I'm new to the list and I just searched through the archives as best I
> could to see if someone else had already brought this up, but I didn't find
> anything. Forgive me if this horse has been beaten.
> I find that typing \(var) is very disruptive to my typing flow. The more I
> code in Swift, the more I like it, but every time I'm coding and then have
> to hiccup while typing \ then ( causes me to be annoyed. I know, it's
> minor, but it isn't a key combination that flows quickly.
> I would much rather have $() or perhaps ${} (like Groovy lang) or perhaps
> @() to go along with other uses of @ throughout the language.
> A shifted key, like $ or @, followed by another shifted key like (, allows
> for a much faster flow and they are much closer to the home keys than \
> which is nearly as far from home keys as possible (and awkward).
> Thoughts?
> Kenny Wyland
> InADayDevelopment.com
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

Joseph Bell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160626/f1218186/attachment.html>

More information about the swift-evolution mailing list