March 28, 2012 marks an important milestone in the development of the Go programming language. We announce Go version 1, or Go 1 for short, which defines a language and a core set of libraries that provide a stable foundation for creating reliable products, projects, and publications. (recommended learning: go)
Go 1 is the first release of Go, providing binary packages. Available for Linux, FreeBSD, Mac OS X and very excitingly - Windows.
For users, Go 1 is quite stable to control. Anyone writing a Go 1 program can be completely confident that in most circumstances, the program will still compile and run years later without any modifications.
Similarly, people who write books about Go 1 can be sure that their examples and explanations will be helpful to readers today and in the future.
Forward compatibility is part of stability. Code compiled by Go 1 should (with few exceptions) be able to continue to compile and run during the life of this version, such as Go versions 1.1, 1.2, etc. produced for issue updates and bug fixes. , the Go 1 compatibility document explains the compatibility guidelines in more detail.
Go 1 is a representation of Go's current use, not a major refactor. As part of the plan, we are focusing on cleaning up issues and inconsistencies and improving portability. It's been a long time since we originally designed and prototyped Go, and a lot of changes have happened, and the reason they weren't released is because they weren't backwards compatible.
Go 1 contains changes that provide significant improvements to the language and libraries, but are not compatible with older programs. Fortunately, the go fix tool can automate much of the work of upgrading your program to the Go 1 standard.
Go 1 brings changes to the language (such as Unicode characters and the new errors type) and the standard library (such as the new time package and the renaming of the strconv package). At the same time, the package hierarchy has been sorted out so that related projects can be put together. For example, network-related rpc packages have been adjusted to the subdirectory of net.
There is a complete list of changes in the Go 1 release notes. This document is an essential guide for migrating from earlier versions of Go.
We also refactored the Go toolkit, using the new go command as a package to obtain, build, install and manage Go code. The go command eliminates the need for a Makefile when writing Go code because it uses the Go program's code itself to drive the build. No more build scripts!
Finally, the release of Go 1 resulted in the release of a new version of Google App Engine SDK. A similar revision and stabilization process has been applied to App Engine packages, providing developers with the building blocks for building programs that can run on App Engine for many years.
Go 1 is the result of a joint effort between the Go core group and contributors from the open source community. We would like to express our gratitude to everyone who has helped.
There is no time more suitable to become a Go programmer than now. Everything you need to take the first step is at golang.org.
The above is the detailed content of When was golang version 1 invented?. For more information, please follow other related articles on the PHP Chinese website!