Go'ing Insane Part Three: Imperfect Interfaces

1. go

   1 2,255 127,368 10.0 Go

   The Go programming language

   

   The explanation you refer to later in the piece assumes we are using fat pointers, but the earlier part is referring to the use of fat pointers in the first place (or more broadly the lack of covariance). Taking a look at https://github.com/golang/go/issues/7512 it looks like the lack of covariance stays because of the complexity cost in the language to support it

2. InfluxDB

   influxdata.com featured

   InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.

   

3. guide

   2 28 16,421 3.7 Makefile

   The Uber Go Style Guide.

   

   Yes it is: https://github.com/uber-go/guide/issues/25

4. ireturn

   3 1 65 5.8 Go

   Accept Interfaces, Return Concrete Types

   

   Can I highjack a topic? Made a linter recently that will track usage of returned values, just to follow rule return concrete values instead interfaces- ireturn. Can be configurable, can be used with github-actions and will be available with next minor version of golangci-lint.

Suggest a related project