Go'ing Insane Part Three: Imperfect Interfaces

• go

  2,067 119,564 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

• guide

  26 15,218 5.2 Makefile

  The Uber Go Style Guide.

  

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

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• ireturn

  1 50 7.3 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