mirror of
https://github.com/golang/go
synced 2024-11-06 14:26:22 -07:00
b7041c7ad1
Having the proposal numbers recorded in the API files should help significantly when it comes time to audit the new API additions at the end of each release cycle. Change-Id: Id18e8cbdf892228a10ac17e4e21c7e17de5d4ff7 Reviewed-on: https://go-review.googlesource.com/c/go/+/392414 Trust: Russ Cox <rsc@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
24 lines
1.1 KiB
Plaintext
24 lines
1.1 KiB
Plaintext
Files in this directory are data for Go's API checker ("go tool api", in src/cmd/api).
|
|
|
|
Each file is a list of API features, one per line.
|
|
|
|
go1.txt (and similarly named files) are frozen once a version has been
|
|
shipped. Each file adds new lines but does not remove any.
|
|
|
|
except.txt lists features that may disappear without breaking true
|
|
compatibility.
|
|
|
|
Starting with go1.19.txt, each API feature line must end in "#nnnnn"
|
|
giving the GitHub issue number of the proposal issue that accepted
|
|
the new API. This helps with our end-of-cycle audit of new APIs.
|
|
The same requirement applies to next/* (described below), which will
|
|
become a go1.XX.txt for XX >= 19.
|
|
|
|
The next/ directory contains the only files intended to be mutated.
|
|
Each file in that directory contains a list of features that may be added
|
|
to the next release of Go. The files in this directory only affect the
|
|
warning output from the go api tool. Each file should be named
|
|
nnnnn.txt, after the issue number for the accepted proposal.
|
|
(The #nnnnn suffix must also appear at the end of each line in the file;
|
|
that will be preserved when next/*.txt is concatenated into go1.XX.txt.)
|