golang泛型_泛型是Go的泛型.pdfVIP

golang泛型_泛型是Go的泛型 golang 泛型 About three years ago, I was working on a pull request approval manager for GitHub written in Go called . While building out the integration layer, I came across a situation where the straightforward approach in Go was overly repetitive. The ideal solution would have been to use generics, but they weren’t available. ⼤约三年前，我正在为Go编写⼀个名为 GitHub的请求请求批准管理器。 在构建集成层时，我遇到了⼀种情况，即Go中简单的⽅法过于重 复。 理想的解决⽅案是使⽤泛型，但它们不可⽤。 However, I figured out that in many cases, you can use closures to pass values. I described my experience with this problem, and my solution in a and a , both called Closures are the Generics of Go. 但是，我发现在许多情况下，可以使⽤闭包来传递值。 我在和描述了我在此问题上的经验，并提出了解决⽅案，它们都称为Closures是Go 的泛型。 Things are about to change. The Go team has released a and a that describe a potential implementation of generics for Go. The draft proposal uses parameterized types to add most of the generics functionality that people have requested, without changing the fundamental character of Go. 事情将要改变。 Go团队发布了和 ，描述了Go泛型的潜在实现。 提案草案使⽤参数化类型来添加⼈们所要求的⼤多数泛型功能，⽽不会改 变Go的基本特征。 在Go语⾔中引⼊泛型 (Introducing Generics in Go) The Go team also values backwards compatibility; old code should continue to work so that it can be maintained for years. The generics draft was written with these goals in mind. Go团队还重视向后兼容性。 旧代码应继续⼯作，以便可以保留多年。 编写通⽤专利草案时就牢记了这些⽬标。 a user-defined container type We’ll start our look at Go generics by trying out the simplest case: . We’ll use a linked list as our sample container type. Here’s what it looks like to write one in Go today: ⽤户定义的容器类型 我们将通过尝试最简单的情况开始研究Go泛型 ： 。 我们将使⽤链接列表作为⽰例容器类型。 这是今天在Go中编写⼀ 个代码的样⼦： type LinkedList struct { value interface{} next *LinkedList } And here’s what that looks like when usi