Golang News

Go Experience Reports #go2 #experiencereport

Fri, 18 Aug 2017 10:18:00 +0000

This page collects experience reports about problems with Go that might inform our design of solutions to those problems. These reports should focus on the problems: they should not focus on and need not propose solutions. To propose solutions, see the proposal process.

We hope to use these experience reports to understand where people are having trouble writing Go, to help us prioritize future changes to the Go ecosystem. (We do not promise to reply to these. If you need immediate help answering questions about Go, see https://golang.org/help/ for resources.)

8 points posted by kenny

When Go’s type system impedes library interoperability #go2 #experiencereports

Thu, 07 Sep 2017 16:16:00 +0000

6 points posted by kenny

Go experience report for generics: google metrics api #experiencereport

Sat, 26 Aug 2017 05:45:00 +0000

This report describes my experience designing, implementing, and deploying a Go API for instrumenting programs with metrics for production monitoring. The C++ and Java APIs used templates and generics; since Go lacks those features, we developed an API that requires some runtime checks. Those runtime checks eventually caused failures in production, requiring us to replace them with logging and monitoring instead. Those failures could have been avoided altogether with support for generics in Go. 6 points posted by kenny

Why context.Value matters and how to improve it #go2 #experiencereport

Mon, 14 Aug 2017 08:48:00 +0000

6 points posted by daenney

A use case for Go generics in a Go compiler #experiencereport #go2

Thu, 10 Aug 2017 13:51:00 +0000

This is a (very) rare work-related entry. I mostly work on the compiler for a programming language named “Go”, and one of the problems we face is if and how we should add “generics” to a future version of Go. I can’t possibly summarize easily for a non-technical reader, but the TLDR version is (1) lots of other languages have generics (2) we’re pretty sure they’re useful (3) but they come with associated costs and complexity and we’re not sure they’re worth it. Also, “generics” is not just a single thing, there’s several semantic variants and several ways to implement them (for example, erased versus dictionary-passing versus template-stamping). 6 points posted by daenney

Tensor refactor #experiencereports

Tue, 26 Sep 2017 15:21:00 +0000

I recently finished a major refactor of `tensor`, which is a package for generic multidimensional arrays in Go. In this blog post I will recount the refactoring process, and why certain decisions were made. Further more I will also share some thoughts with regards to generics in Go while trying not to sound like a complete prat. 5 points posted by kenny

Why I miss generics in go #experiencereport

Tue, 22 Aug 2017 14:25:00 +0000

5 points posted by lolly