From 43a123c1ae6613b3efeed291fa552ecd909d3acf Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 16 Apr 2024 21:23:18 +0200 Subject: Adding upstream version 1.20.14. Signed-off-by: Daniel Baumann --- api/README | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 api/README (limited to 'api/README') diff --git a/api/README b/api/README new file mode 100644 index 0000000..1e52f7a --- /dev/null +++ b/api/README @@ -0,0 +1,23 @@ +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.) -- cgit v1.2.3