Go Language: w/rt/ Pike, strings, runes, byte slices, see also
On Sat, Aug 12, 2017 at 12:28 AM, John Yeung <gallium.arsenide@xxxxxxxxx>
On Fri, Aug 11, 2017 at 7:54 PM, Jack Woehr
Go Language goes even further in this direction.
Goes further in which direction? Judging by this:
I would say that Go has gone in the opposite direction as Python.
Which I think is understandable, given the design and intended uses of
Go. Particularly telling is this philosophical difference between Go
and Python 3:
In fact, the definition of "character" is ambiguous and it would be a
mistake to try to resolve the ambiguity by defining that strings are
made of characters.
But the creator of Python spent a long and arduous year specifically
working on the problem of how to define strings so that they ARE made
of *characters*, and NOT bytes. He felt so strongly about this that he
risked fracturing the Python community by breaking compatibility with
Python 2 to accomplish this.
While diametrically opposed, I guess what Go shares with Python 3 is
the clear distinction between bytes and characters. (At least, I am
trusting that this is the case with Go, given that blog post by none
other than Rob Pike.) Many languages conflate bytes and strings, and
that may well be worse than being clearly on one side of the fence or
the other (at least in the post-ASCII world we live in today).
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.