-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unicode: support version 13 #40755
Comments
If the process of regenerating the code is documented somewhere, I am ready to try and send a CL myself. |
Change https://golang.org/cl/248765 mentions this issue: |
I second the question: where is the procedure documented to generate the CL? My motivation to knowing is not concerned with generating the update CL but more how to change the process to potentially generate more binary size efficient datastructures for the unicode package. |
Fixes golang#40755 Change-Id: I14b3977317994095db8ae1bd873c174641209356 Reviewed-on: https://go-review.googlesource.com/c/go/+/248765 Run-TryBot: Marcel van Lohuizen <mpvl@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
Fixes golang#40755 Change-Id: I14b3977317994095db8ae1bd873c174641209356 Reviewed-on: https://go-review.googlesource.com/c/go/+/248765 Run-TryBot: Marcel van Lohuizen <mpvl@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
13.0.0
What did you see instead?
12.0.0
I didn't find a recurring issue for Unicode updates, so I decided to submit this one. Please feel free to close if there is one already.
The text was updated successfully, but these errors were encountered: