mirror of
https://github.com/golang/go.git
synced 2025-05-05 15:43:04 +00:00
1711f953e4
Deprecating an API creates notices that go out to potentially millions of Go developers encouraging them to update their code. The choice to deprecate an API is as important as the choice to add a new API. We should track those and make them explicit. This will also ensure that deprecations go through proposal review. Change-Id: Ide9f60c32e5a88fb133e0dfedd984b8b0f70f510 Reviewed-on: https://go-review.googlesource.com/c/go/+/453259 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
7 lines
321 B
Plaintext
7 lines
321 B
Plaintext
pkg p4, func NewPair[$0 interface{ M }, $1 interface{ ~int }]($0, $1) Pair
|
|
pkg p4, method (Pair[$0, $1]) Second() $1
|
|
pkg p4, method (Pair[$0, $1]) First() $0
|
|
pkg p4, type Pair[$0 interface{ M }, $1 interface{ ~int }] struct
|
|
pkg p4, func Clone[$0 interface{ ~[]$1 }, $1 interface{}]($0) $0
|
|
pkg p4, func Clone //deprecated
|