qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-21 15:34:45 -07:00
Code Releases Activity

weekly.2011-10-26 (new rune type)

Browse Source 
R=rsc
CC=golang-dev
https://golang.org/cl/5297062
This commit is contained in:
Andrew Gerrand 2011-10-26 14:47:38 +09:00
parent c945f77f41
commit 659f1f208a
2 changed files with 20 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.hgtags
View File

@ -89,4 +89,3 @@ c1702f36df0397c19fc333571a771666029aa37e release
acaddf1cea75c059d19b20dbef35b20fb3f38954 release.r58.2
6d7136d74b656ba6e1194853a9486375005227ef weekly.2011-10-18
941b8015061a0f6480954821dd589c60dfe35ed1 weekly.2011-10-25
941b8015061a0f6480954821dd589c60dfe35ed1 weekly

20
doc/devel/weekly.html
View File

@ -14,6 +14,26 @@ hg pull
hg update weekly.<i>YYYY-MM-DD</i>
</pre>
<h2 id="2011-10-26">2011-10-26 (new rune type)</h2>
<pre>
This snapshot introduces the rune type, an alias for int that
should be used for Unicode code points.
A future release of Go (after Go 1) will change rune to be an
alias for int32 instead of int. Using rune consistently is the way
to make your code build both before and after this change.
To test your code for rune safety, you can rebuild the Go tree with
GOEXPERIMENT=rune32 ./all.bash
which builds a compiler in which rune is an alias for int32 instead of int.
Also, run govet on your code to identify methods that might need to have their
signatures updated.
</pre>
<h2 id="2011-10-25">2011-10-25</h2>
<pre>