Error handling and Go - The Go Programming Language
Andrew Gerrand 12 July 2011 Introduction If you have written any Go code you have probably encountered the built-in error type. Go code uses error values to indicate an abnormal state. For example, the os.Open function returns a non-nil error value when it fails to open a file. func Open(name string) (file *File, err error) The following code uses os.Open to open a file. If an error occurs it call
Go Slices: usage and internals - The Go Programming Language
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
Defer, Panic, and Recover - The Go Programming Language
Andrew Gerrand 4 August 2010 Go has the usual mechanisms for control flow: if, for, switch, goto. It also has the go statement to run code in a separate goroutine. Here I’d like to discuss some of the less common ones: defer, panic, and recover. A defer statement pushes a function call onto a list. The list of saved calls is executed after the surrounding function returns. Defer is commonly used t
Inside the Go Playground - The Go Programming Language
The playground service has three parts: A back end that runs on Google’s servers. It receives RPC requests, compiles the user program using the gc tool chain, executes the user program, and returns the program output (or compilation errors) as the RPC response. A front end that runs on Google App Engine. It receives HTTP requests from the client and makes corresponding RPC requests to the back end
Go: a simple programming environment
Go: a simple programming environment 9 Nov 2012 Andrew Gerrand Google Inc. Video A video of this talk was recorded at Øredev in Malmö, Sweden in November 2012. Watch the talk on Vimeo 2 Background 3 Why a new language? Motivated by our needs at Google. We need: Efficiency Safety Concurrency Scalability Fast development cycle No surprises A cute mascot 4 Design "Consensus drove the design. Nothing
What's in a name?
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
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
First Class Functions in Go - The Go Programming Language
