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



OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The article explains how to use the pprof tool for analyzing Go performance, including enabling profiling, collecting data, and identifying common bottlenecks like CPU and memory issues.Character count: 159

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

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

The article discusses the go fmt command in Go programming, which formats code to adhere to official style guidelines. It highlights the importance of go fmt for maintaining code consistency, readability, and reducing style debates. Best practices fo

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...
