What are the scenarios for using Go generics so far?

Today’s article is to collect everyone’s usage scenarios within generics, and let’s tinker with it together. So the title is actually a question.

Go1.18 was officially released on March 15 this year, which means that Go has officially entered the era of generics.

(One less hacked point?)

Nearly 3 months have passed since the release of 1.18, and the most eye-catching new feature is Pan Type, and how is it used?

According to feedback from various gophers on reddit, there are at least the following usage scenarios at this stage:

• Tool libraries such as slicing, mapping, and collection.
• Library for code generators.
• Library for caching layer.
• Libraries related to algorithms and data structures.
• Concurrency manager.
  

Do these scenarios include the Go generic direction you are working on?

Judging from the results of feedback from foreign forums, the promotion of generics is more harmful to the compatibility issue of the gopls/golangci-lint tool, and many lints have not yet been adapted. The new version of generic syntax has very limited support for generics.

The following issues of "Support of go1.18^[1]":

##For golangci abroad -lint has a significantly higher dependency, and is basically a must-run for mature projects. This will lead to the company not allowing it to be used because golangci-lint does not yet support it.

In addition, some students who are more conservative or have no application scenarios are waiting for the support for generics in the standard library of Go1.19 and more general libraries before further using it.

Everyone

Have you ever started using generics in your daily life and in your company? What have you done and what are the scenarios?

Welcome to tell everyone in the comment area and learn and communicate together.

The above is the detailed content of What are the scenarios for using Go generics so far?. For more information, please follow other related articles on the PHP Chinese website!