Tips for writing clear, performant, and idiomatic Go code
Go’s arrays are values. An array variable denotes the entire array; it is not a pointer to the first array element (as would be the case in C). This means that when you assign or pass around an array value you will make a copy of its contents. (To avoid the copy you could pass a pointer to the array, but then that’s a pointer to an array, not an array.) One way to think about arrays is as a sort o
What's in a name? October 2014 Andrew Gerrand Google Inc. Names matter Readability is the defining quality of good code. Good names are critical to readability. This talk is about naming in Go. 2 Good names A good name is: Consistent (easy to guess), Short (easy to type), Accurate (easy to understand). 3 A rule of thumb The greater the distance between a name's declaration and its uses, the longer
David Crawshaw 18 August 2016 Introduction Go was designed for writing servers. That is how it is most widely used today, and as a result a lot of work on the runtime and compiler is focused on issues that matter to servers: latency, ease of deployment, precise garbage collection, fast startup time, performance. As Go gets used for a wider variety of programs, there are new issues that must be con
The State of Go Where we are in February 2015 Andrew Gerrand Go 1.4 Released in December 2014. A few important things: Android support. Canonical import paths. The go generate command. Lots of behind-the-scenes work: Prep work for new garbage collector. Prep work for C to Go tool chain conversion. Source tree re-organization. go.dev/doc/go1.4 2 Transition to Git 3 Transition to Git In December we
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く