Context isn’t for cancellation | Dave Cheney
This is an experience report about the use of, and difficulties with, the context.Context facility in Go. Many authors, including myself, have written about the use of, misuse of, and how they would change, context.Context in a future iteration of Go. While opinions differs on many aspects of context.Context, one thing is clear–there is almost unanimous agreement that the Context.WithValue method
Padding is hard | Dave Cheney
Hmm, so some progress. We’ve managed to reduce the storage in the Go 1.5 64 bit case, but the others appear unchanged, especially Go 1.5’s 32 bit case. For the Go 1.5 64 bit case, the padding that we saw above is still there, but it has moved. Effectively what the compiler is seeing is this: type ProgInfo struct { Reguse uint64 // registers implicitly used by this instruction Regset uint64 // regi
Inspecting errors | Dave Cheney
The common contract for functions which return a value of the interface type error, is the caller should not presume anything about the state of the other values returned from that call without first checking the error. In the majority of cases, error values returned from functions should be opaque to the caller. That is to say, a test that error is nil indicates if the call succeeded or failed, a
Gocon Spring 2016
Good morning! Thank you for coming to my talk. Before I begin, I want to express my gratitude to tenntenn and the organisers of GoCon for inviting me to speak today. I also want to acknowledge the generous sponsorship of our hosts, Cyber Agent, for providing the venue for today. [ to audience ] would someone be kind enough to read this for me ? Do you know the english translation? A frog in a well
Stack traces and the errors package | Dave Cheney
A few months ago I gave a presentation on my philosophy for error handling. In the talk I introduced a small errors package designed to support the ideas presented in the talk. This post is an update to my previous blog post which reflects the changes in the errors package as I’ve put it into service in my own projects. Wrapping and stack traces In my April presentation I gave examples of using th
Let’s talk about logging | Dave Cheney
This is a post inspired by a thread that Nate Finch started on the Go Forum. This post focuses on Go, but if you can see your way past that, I think the ideas presented here are widely applicable. Why no love ? Go’s log package doesn’t have leveled logs, you have to manually add prefixes like debug, info, warn, and error, yourself. Also, Go’s logger type doesn’t have a way to turn these various le
Performance without the event loop | Dave Cheney
This article is also available in Japanese, イベントループなしでのハイパフォーマンス – C10K問題へのGoの回答 This article is based on a presentation I gave earlier this year at OSCON. It has been edited for brevity and to address some of the points of feedback I received after the talk. A common refrain when talking about Go is it’s a language that works well on the server; static binaries, powerful concurrency, and high per
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
How to install Go 1.1 on CentOS 5.9 | Dave Cheney