Tips for writing clear, performant, and idiomatic Go code
Julie Qiu 15 June 2020 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
Damien Neil and Jonathan Amsterdam 17 October 2019 Introduction Go’s treatment of errors as values has served us well over the last decade. Although the standard library’s support for errors has been minimal—just the errors.New and fmt.Errorf functions, which produce errors that contain only a message—the built-in error interface allows Go programmers to add whatever information they desire. All i
Tyler Bui-Palsulich 26 September 2019 Introduction This post is part 3 in a series. Part 1 — Using Go Modules Part 2 — Migrating To Go Modules Part 3 — Publishing Go Modules (this post) Part 4 — Go Modules: v2 and Beyond Part 5 — Keeping Your Modules Compatible Note: For documentation on developing modules, see Developing and publishing modules. This post discusses how to write and publish modules
David Chase 21 March 2019 Introduction Go 1.11 and Go 1.12 make significant progress toward allowing developers to debug the same optimized binaries that they deploy to production. As the Go compiler has become increasingly aggressive in producing faster binaries, we’ve lost ground in debuggability. In Go 1.10, users needed to disable optimizations entirely in order to have a good debugging experi
Steve Francia, for the Go team 6 March 2017 Thank you This post summarizes the result of our December 2016 user survey along with our commentary and insights. We are grateful to everyone who provided their feedback through the survey to help shape the future of Go. Programming background Of the 3,595 survey respondents, 89% said they program in Go at work or outside of work, with 39% using Go both
When in Go, do as Gophers do Go Conference 2014 autumn 30 November 2014 Fumitoshi Ukai Google Software Engineer - Chrome Infra team Go Readability Approver A team to review Go readability. help to learn idiomatic Go though code review review code of projects that are not main project of the reviewer I joined the team about a year ago as 20% time, and reviewed ~200 CLs For now, I'm reviewing at mos
Chris Broadfoot 16 February 2017 Today the Go team is happy to announce the release of Go 1.8. You can get it from the download page. There are significant performance improvements and changes across the standard library. The compiler back end introduced in Go 1.7 for 64-bit x86 is now used on all architectures, and those architectures should see significant performance improvements. For instance,
Introduction Go is a new language. Although it borrows ideas from existing languages, it has unusual properties that make effective Go programs different in character from programs written in its relatives. A straightforward translation of a C++ or Java program into Go is unlikely to produce a satisfactory result—Java programs are written in Java, not Go. On the other hand, thinking about the prob
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く