Go: When To Use Generics

[NewsBot]

A new Go blog post/announcement has been posted!

<div class="Article" data-slug="/blog/when-generics">

<h1 class="small"><a href="/blog/">The Go Blog</a></h1>


<h1>When To Use Generics</h1>
  
  <p class="author">
  Ian Lance Taylor<br>
  12 April 2022
  </p>
  
  <h2 id="introduction">Introduction</h2>

This is the blog post version of my talks at Google Open Source Live:

and GopherCon 2021:

The Go 1.18 release adds a major new language feature: support for generic programming. In this article I’m not going to d...

Get the full details here: When To Use Generics - The Go Programming Language

[bot]

Corresponding tweet for this thread:

Devtalk

Share link for this tweet.

[OvermindDL1]

Let’s start with a general guideline for programming Go: write Go programs by writing code, not by defining types.

This is utterly horrifying and is one of the worst things about the whole go model.

Programs are something that translate data from one format to another, generally by a whole series of transformations internally. Not thinking about your data model from the beginning is horrifying. Types should come first, so you know that it is in a good format at every step. Then and only then do you write transformations (functions) between them.