From: Russ Cox
- As announced in the Go 1.20 release notes, - Go 1.21 requires macOS 10.15 Catalina or later; - support for previous versions has been discontinued. -
- -- As announced in the Go 1.20 release notes, - Go 1.21 requires at least Windows 10 or Windows Server 2016; - support for previous versions has been discontinued. -
- - -- -
- -
- The new go:wasmimport
directive can now be used in Go programs
- to import functions from the WebAssembly host.
-
- The Go scheduler now interacts much more efficiently with the - JavaScript event loop, especially in applications that block - frequently on asynchronous events. -
- - -
- Go 1.21 adds an experimental port to the
- WebAssembly System Interface (WASI), Preview 1
- (GOOS=wasip1
, GOARCH=wasm
).
-
- As a result of the addition of the new GOOS
value
- "wasip1
", Go files named *_wasip1.go
- will now be ignored
- by Go tools except when that GOOS
value is being
- used.
- If you have existing filenames matching that pattern, you will
- need to rename them.
-
+ As announced in the Go 1.20 release notes, + Go 1.21 requires macOS 10.15 Catalina or later; + support for previous versions has been discontinued. +
+ ++ As announced in the Go 1.20 release notes, + Go 1.21 requires at least Windows 10 or Windows Server 2016; + support for previous versions has been discontinued. +
+ + ++ +
+ +
+ The new go:wasmimport
directive can now be used in Go programs
+ to import functions from the WebAssembly host.
+
+ The Go scheduler now interacts much more efficiently with the + JavaScript event loop, especially in applications that block + frequently on asynchronous events. +
+ + +
+ Go 1.21 adds an experimental port to the
+ WebAssembly System Interface (WASI), Preview 1
+ (GOOS=wasip1
, GOARCH=wasm
).
+
+ As a result of the addition of the new GOOS
value
+ "wasip1
", Go files named *_wasip1.go
+ will now be ignored
+ by Go tools except when that GOOS
value is being
+ used.
+ If you have existing filenames matching that pattern, you will
+ need to rename them.
+