|author||Jonathan Amsterdam <firstname.lastname@example.org>||Mon Oct 14 06:28:25 2019 -0400|
|committer||Jonathan Amsterdam <email@example.com>||Mon Oct 14 17:15:48 2019 +0000|
cmd/apidiff: store package path with export data BREAKING CHANGE: If you have old files saved with -w, they will no longer work. When writing export data for a package, save the path of the package. The export data format doesn't store this information. Previously it didn't matter, because gcexportdata.Reader.Read would return the package that was written. But since golang.org/cl/198742, that is no longer true. This was apidiff's bug, not gcexportdata's: for the path argument of Read I was passing garbage (the filename) rather than the import path. Read's doc doesn't specify what happens if you do that. Also, update golang.org/x/tools to latest. Fixes golang/go#34849. Change-Id: I9d590270a9c2bb1fcc6c9071d4a2ca82c85d84d6 Reviewed-on: https://go-review.googlesource.com/c/exp/+/200997 Reviewed-by: Jay Conrod <firstname.lastname@example.org>
This subrepository holds experimental and deprecated (in the
old directory) packages.
The idea for this subrepository originated as the
pkg/exp directory of the main repository, but its presence there made it unavailable to users of the binary downloads of the Go installation. The subrepository has therefore been created to make it possible to
go get these packages.
Warning: Packages here are experimental and unreliable. Some may one day be promoted to the main repository or other subrepository, or they may be modified arbitrarily or even disappear altogether.
In short, code in this subrepository is not subject to the Go 1 compatibility promise. (No subrepo is, but the promise is even more likely to be violated by go.exp than the others.)