2012-05-22 19:41:20 -06:00
|
|
|
Files in this directory are data for Go's API checker ("go tool api", in src/cmd/api).
|
|
|
|
|
|
2015-12-18 21:00:12 -07:00
|
|
|
Each file is a list of API features, one per line.
|
2012-05-22 19:41:20 -06:00
|
|
|
|
|
|
|
|
go1.txt (and similarly named files) are frozen once a version has been
|
|
|
|
|
shipped. Each file adds new lines but does not remove any.
|
|
|
|
|
|
2013-02-11 10:10:35 -07:00
|
|
|
except.txt lists features that may disappear without breaking true
|
|
|
|
|
compatibility.
|
2012-10-03 19:35:17 -06:00
|
|
|
|
2022-03-14 09:03:23 -06:00
|
|
|
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.)
|
