|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | - | - |
| README | D | 25-Apr-2025 | 1.2 KiB | 27 | 20 |
| except.txt | D | 25-Apr-2025 | 34.8 KiB | 605 | 604 |
| go1.1.txt | D | 25-Apr-2025 | 2.6 MiB | 50,455 | 50,454 |
| go1.10.txt | D | 25-Apr-2025 | 30.1 KiB | 628 | 627 |
| go1.11.txt | D | 25-Apr-2025 | 25 KiB | 560 | 559 |
| go1.12.txt | D | 25-Apr-2025 | 13.5 KiB | 229 | 228 |
| go1.13.txt | D | 25-Apr-2025 | 452.6 KiB | 8,033 | 8,032 |
| go1.14.txt | D | 25-Apr-2025 | 508.9 KiB | 8,915 | 8,914 |
| go1.15.txt | D | 25-Apr-2025 | 7.6 KiB | 131 | 130 |
| go1.16.txt | D | 25-Apr-2025 | 479.2 KiB | 8,528 | 8,527 |
| go1.17.txt | D | 25-Apr-2025 | 18 KiB | 304 | 303 |
| go1.18.txt | D | 25-Apr-2025 | 13 KiB | 254 | 253 |
| go1.19.txt | D | 25-Apr-2025 | 17.9 KiB | 310 | 309 |
| go1.2.txt | D | 25-Apr-2025 | 1.9 MiB | 32,485 | 32,484 |
| go1.20.txt | D | 25-Apr-2025 | 602.6 KiB | 9,166 | 9,165 |
| go1.21.txt | D | 25-Apr-2025 | 25.6 KiB | 427 | 426 |
| go1.22.txt | D | 25-Apr-2025 | 7.7 KiB | 136 | 135 |
| go1.23.txt | D | 25-Apr-2025 | 10.1 KiB | 159 | 158 |
| go1.3.txt | D | 25-Apr-2025 | 117 KiB | 2,054 | 2,053 |
| go1.4.txt | D | 25-Apr-2025 | 34 KiB | 605 | 565 |
| go1.5.txt | D | 25-Apr-2025 | 46.6 KiB | 976 | 975 |
| go1.6.txt | D | 25-Apr-2025 | 12.9 KiB | 276 | 275 |
| go1.7.txt | D | 25-Apr-2025 | 13.6 KiB | 286 | 285 |
| go1.8.txt | D | 25-Apr-2025 | 16.3 KiB | 262 | 261 |
| go1.9.txt | D | 25-Apr-2025 | 10.7 KiB | 197 | 196 |
| go1.txt | D | 25-Apr-2025 | 1.7 MiB | 30,872 | 30,871 |
README
1Files in this directory are data for Go's API checker ("go tool api", in src/cmd/api).
2
3Each file is a list of API features, one per line.
4
5go1.txt (and similarly named files) are frozen once a version has been
6shipped. Each file adds new lines but does not remove any.
7
8except.txt lists features that may disappear without breaking true
9compatibility.
10
11Starting with go1.19.txt, each API feature line must end in "#nnnnn"
12giving the GitHub issue number of the proposal issue that accepted
13the new API. This helps with our end-of-cycle audit of new APIs.
14The same requirement applies to next/* (described below), which will
15become a go1.XX.txt for XX >= 19.
16
17The next/ directory contains the only files intended to be mutated.
18Each file in that directory contains a list of features that may be added
19to the next release of Go. The files in this directory only affect the
20warning output from the go api tool. Each file should be named
21nnnnn.txt, after the issue number for the accepted proposal.
22(The #nnnnn suffix must also appear at the end of each line in the file;
23that will be preserved when next/*.txt is concatenated into go1.XX.txt.)
24
25When you add a file to the api/next directory, you must add at least one file
26under doc/next. See doc/README.md for details.
27