Twelve Years of Go - The Go Programming Language
Today we celebrate the twelfth birthday of the Go open source release. We have had an eventful year and have a lot to look forward to next year. The most visible change here on the blog is our new home on go.dev, part of consolidating all our Go web sites into a single, coherent site. Another part of that consolidation was replacing godoc.org with pkg.go.dev. In February, the Go 1.16 release added
Gopls on by default in the VS Code Go extension - The Go Programming Language
(gopls provides IDE features, such as intelligent autocompletion, signature help, refactoring, and workspace symbol search.) When Go modules were released two years ago, they completely changed the landscape of Go developer tooling. Tools like goimports and godef previously depended on the fact that code was stored in your $GOPATH. When the Go team began rewriting these tools to work with modules,
Pkg.go.dev is open source! - The Go Programming Language
We’re excited to announce that the codebase for pkg.go.dev is now open source. The repository lives at go.googlesource.com/pkgsite and is mirrored to github.com/golang/pkgsite. We will continue using the Go issue tracker to track feedback related to pkg.go.dev. Contributing If you are interested in contributing to any issues related to pkg.go.dev, check out our contribution guidelines. We also enc
Mariano Gappa's Blog
TL;DRThis is the story of how I managed to expose my Golang chess API project cheesse as a WebAssembly binary, compiled using TinyGo, so JavaScript could use it without needing a server. The blogpost is optimised for helping others going through a similar exercise, rather than for readability, so expect a little too much of “if this, do this”. Sorry. What are all those technologies?WebAssembly Ass
The Go low-level calling convention on x86-64
Note The latest version of this document can be found online at https://dr-knz.net/go-calling-convention-x86-64.html. Alternate formats: Source, PDF. Introduction This article analyzes how the Go compiler generates code for function calls, argument passing and exception handling on x86-64 targets. This expressely does not analyze how the Go compiler lays out data in memory (other than function arg
GopherJS vs WebAssembly for Go
EDIT: For the latest of GopherJS/Wasm comparison, see Wasm benchmark result Hi all! This article describes about my experiment of the new WebAssembly port of Go. WebAssembly port is now available on the master branch of Go, and you'd need to compile Go yourself. tl;dr I have created GopherWasm, an agnostic WebAssembly wrapper that works both on GopherJS and WebAssembly port. Performance of GopherJ
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
