Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
The only real issue I could see would be if a Unicode character moved in or out of class Lu or out of classes Ll, Lt, Lm, Lo, or Nd. If we want to be really precise we should list those as possibly breaking backward compatibility for Go 1 source code. I don't think we should worry about the fact that future Unicode standards could change the behaviour of Go 1 programs that use the unicode package. I think that is an acceptable sort of package change, even though it will cause program behaviour to change. I don't think we need to mention this specifically.
Marking this Later, given the disinclination to update. The people who need Meroitic Cursive will have to wait. I did a trial maketables to skim the diffs. The most significant change in Unicode 6.1.0 (beyond putting blank lines in CaseFolding.txt and thereby breaking maketables) is that the ordinal indicators ª º are now Lo instead of Ll. This breaks the assumption in IsLetter that all Latin-1 letters are either Ll or Lu, which will mean adding a way to express that in the properties table, but we're out of bits. Probably we could use pLl|pLu to mean Lo. If you want to see the diffs, http://golang.org/cl/5616077/diff/3/src/pkg/unicode/tables.go
Labels changed: added priority-later, removed priority-go1.