Home >Backend Development >Golang >What has been changed in golang1.11?
As announced in the Go 1.10 release notes, Go 1.11 now requires OpenBSD 6.2 or higher, macOS 10.10 Yosemite or higher, or Windows 7 or higher Later versions; support for earlier versions of these operating systems has been removed.
- msan now supports memory cleaner() linux/arm64. ” c-archivefreebsd/amd64On 64-bit MIPS systems, the new environment variable settings GOMIPS64=hardfloat (the default) and GOMIPS64=softfloat select whether to use hardware instructions or software emulation for floating-point calculations. For 32-bit systems, the environment variable is still GOMIPS since it was added in Go 1.10.
On soft floating point ARM systems (GOARM=5), Go now uses a more efficient software floating point interface. This is transparent to Go code, but ARM assemblies using floating point instructions that are not GOARM protected will break and must be ported to the new interface.
Running 1.11 on ARMv7 no longer requires configuring Linux kernel KUSER_HELPERS. This setting is enabled in the default kernel configuration, but is sometimes disabled in thin configuration.
Web AssemblyGo 1.11 adds an experimental port to WebAssembly (js/wasm). Go programs can currently be compiled into a WebAssembly module, which includes the Go runtime for goroutine scheduling, garbage collection, maps, etc. So the result size is at least about 2 MB, or 500 KB compressed. Go programs can call JavaScript using the new experimental syscall/js package. Binary size and interop with other languages are not yet a priority, but may be addressed in future releases.
Due to the addition of the new GOOS value "js" and GOARCH value "wasm", the Go tool will now ignore Go files named *_js.go or unless those GOOS/GOARCH values are used. If you already have file names matching these patterns, you will need to rename them. *_wasm.go
Modules, package versioning and dependency managementGo 1.11 adds initial support for a new concept called "modules", which are Alternative to GOPATH with integrated support for version control and package distribution. Using modules, developers are no longer limited to working in a GOPATH, version dependency information is clear and lightweight, and builds are more reliable and reproducible. Module support is considered experimental. Details may change based on feedback from Go 1.11 users, and we have more tools planned. Although the details of module support may change, projects converted to modules using Go 1.11 will continue to work in Go 1.12 and later.
Build cache requirementsGo 1.11 will be the latest version to support setting the environment variable GOCACHE=off to disable the build cache. This feature was introduced in Go 1.10. Starting with Go 1.12, the cache will need to be built, which is a step that eliminates $GOPATH/pkg. The module and package loading support described above already requires that the build cache be enabled.
The above is the detailed content of What has been changed in golang1.11?. For more information, please follow other related articles on the PHP Chinese website!