From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Tue,  3 Dec 2013 10:04:14 -0500
To: skip.tavakkolian@gmail.com, 9fans@9fans.net
Message-ID: <a31178143833708633b2811e78d5497f@brasstown.quanstro.net>
In-Reply-To: <CAJSxfmKBADh6kNgqh=uhQFp01h18ndkEuYDmS8WgJjDX=RxLEw@mail.gmail.com>
References: <CAJSxfmK1LD8AMJNGGnmW7ZC5Vh2uzr6ZtV1uogJt-DR7jvbZGQ@mail.gmail.com>
	<8286dc5b2020021773af3b8b0a73ee9e@proxima.alt.za>
	<CAJSxfmKBADh6kNgqh=uhQFp01h18ndkEuYDmS8WgJjDX=RxLEw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Go and 21-bit runes (and a bit of Go status)
Topicbox-Message-UUID: 915c6062-ead8-11e9-9d60-3106f5b1d025

> BTW, another big item that I forgot to mention, which ironically has been
> the Subject of this thread, is the support for 21bit runes.

that was the trigger for getting them into sources,
but unicode specifies a 21-bit rune.  we were wrong.
and both 9atom and p9p had 21-bit runes several years
before they were added to sources.

by the way, the sources version of sort is broken wrt 21-bit runes.
i believe the 9atom version was correct.  somehow the sources
version got messed up.

- erik