Golang News

Video: Russ Cox - The Future of Go #gophercon #go2

Tue, 25 Jul 2017 07:58:00 +0000

Let's start talking about what we - the Go community - might want to change about Go. 23 points posted by gopher

Video: Rob Pike - Go 2 Draft Specifications #go2

Wed, 14 Nov 2018 04:23:00 +0000

18 points posted by gusan-

Video: The Future Of Go - talk by @rob_pike and Q&A #go2

Thu, 17 Aug 2017 13:33:00 +0000

Talk at the Sydney Go Meetup Group in 2017

Part 2 video of the continuing Q&A has some interesting questions/answers

17 points posted by kenny

Context should go away in Go 2 #go2

Mon, 07 Aug 2017 15:28:00 +0000

As usual, when a new blog post comes out on blog.golang.org, I’m all eager to read it as soon as possible. The most recent one, Contributors Summit, is a nice write-up on the issues that the Go contributors have been talking about. While reading it, I stumbled upon a sentence that made me write this post. Here is is: 16 points posted by daenney

Toward Go 2 #releases #go2

Thu, 13 Jul 2017 17:38:00 +0000

This is the text of my talk today at Gophercon 2017, asking for the entire Go community's help as we discuss and plan Go 2. We will add a link to the video when it becomes available. 15 points posted by kenny

Go, Gardening, and Contribution with Brad Fitzpatrick #gotime #go2

Fri, 28 Apr 2017 10:11:00 +0000

Brad Fitzpatrick joined the show to talk about becoming the face of open source Go, getting the community involved in bug triage, the potential future of Go and Go 2.0, and other interesting Go projects and news. 15 points posted by kenny

Go2 here we come #go2

Thu, 29 Nov 2018 19:37:00 +0000

11 points posted by kenny

Typed nils for Go 2 #proposal #go2

Wed, 09 Aug 2017 11:31:00 +0000

11 points posted by daenney

Go experience report: the append function #generics #append #go2

Tue, 18 Jul 2017 06:14:00 +0000

Ian Lance Taylor talks about adding the append function. When the Go language was first publicly released it contained a package named container/vector. The type vector.Vector was a name for the type []interface{}. Vector supported methods like Len, Cap, At, Set, Insert, Delete, Push, Pop, and several more. You can see the source code at on Github. An interesting aspect of the package is that string and int versions of Vector were automatically generated by copying the file vector.go with edits applied by gofmt -r.

10 points posted by kenny

Go 2 contracts are too clever #go2

Sun, 25 Nov 2018 16:10:00 +0000

9 points posted by kenny

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

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

A Goroutine Scoped Context Proposal #concurrency #go2

Sat, 13 Oct 2018 18:30:00 +0000

The context design in Go is beautiful and powerful. But like all things, it also can be improved. In this post I will present the major problems I currently see in the context system, a backward compatible solution to those problems, and a proof of concept library that implements a demo of the solution. Hopefully, you’ll be convinced that this change is necessary and can improve the user experience in the Go language.

4 points posted by drogo

GenX: Generics For Go, Yet Again. #generics #go2

Sun, 27 Aug 2017 13:53:00 +0000

A slightly more powerful generic code generator with a very simple interface.

Features:

* It can be *easily* used with `go generate`, from the command line or as a library.
* `cmd/genx` Uses local files, packages, and optionally uses `go get` (with the `-get` flag) if the remote package doesn't exist.
* You can rewrite, remove and change pretty much everything.
* Allows you to merge a package of multiple files into a single one.
* *Safely* remove functions and struct fields.
* Automatically passes all code through `x/tools/imports` (aka `goimports`).
* If you intend on generating files in the same package, you may add `// +build genx` to your template(s).
* Transparently handles [genny](https://github.com/cheekybits/genny)'s `generic.Type`.
* Supports a few [seeds](https://github.com/OneOfOne/genx/tree/master/seeds/).
* Adds build tags based on the types you pass, so you can target specifc types (ex: `// +build genx_t_string` or `// +build genx_vt_builtin` )
* Automatically handles nil returns, will return the zero value of the type.
* Doesn't need modifying the source package if there's only one type involved.

4 points posted by OneOfOne