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!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

This article explains Go's package import mechanisms: named imports (e.g., import "fmt") and blank imports (e.g., import _ "fmt"). Named imports make package contents accessible, while blank imports only execute t

This article explains Beego's NewFlash() function for inter-page data transfer in web applications. It focuses on using NewFlash() to display temporary messages (success, error, warning) between controllers, leveraging the session mechanism. Limita

This article details efficient conversion of MySQL query results into Go struct slices. It emphasizes using database/sql's Scan method for optimal performance, avoiding manual parsing. Best practices for struct field mapping using db tags and robus

This article demonstrates creating mocks and stubs in Go for unit testing. It emphasizes using interfaces, provides examples of mock implementations, and discusses best practices like keeping mocks focused and using assertion libraries. The articl

This article explores Go's custom type constraints for generics. It details how interfaces define minimum type requirements for generic functions, improving type safety and code reusability. The article also discusses limitations and best practices

This article details efficient file writing in Go, comparing os.WriteFile (suitable for small files) with os.OpenFile and buffered writes (optimal for large files). It emphasizes robust error handling, using defer, and checking for specific errors.

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

This article explores using tracing tools to analyze Go application execution flow. It discusses manual and automatic instrumentation techniques, comparing tools like Jaeger, Zipkin, and OpenTelemetry, and highlighting effective data visualization
