-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proposal: x/tools/go/gcexportdata: drop experimental bundle API #69573
Comments
Change https://go.dev/cl/614815 mentions this issue: |
CC @jba for apidiff |
Why do you describe apidiff has a few users, notably the Go client libraries for GCP. I don't think we should break it. I'd be happy to rewrite Read/WriteBundle, if you could explain how to get the same effect. |
I misremembered. In any case, it's easy enough for me to fix this one instance. My point was more that no-one is really using this feature. |
Given that it is experimental and we don't think anyone is using it, this seems fine. |
This proposal has been added to the active column of the proposals project |
Change https://go.dev/cl/634600 mentions this issue: |
This CL changes apidiff to stop using the bundle read/write operations, which were always experimental and are in the process of being deprecated/dropped (#69573). Instead, we use the ordinary gcexportdata.Write operation to save each package into a section of a zip file named after the package, in topological order. (This could perhaps be simplified further by simply retaining the export data files originally produced by the compiler without even parsing them; see go/packages.NeedExportFile.) Also: - plumb token.FileSet down from main, addressing a TODO. - remove unnecessary packages.LoadMode bits. Updates golang/go#69573 Change-Id: I6347097b480853d7bf21047595282f2123ee50b1 Reviewed-on: https://go-review.googlesource.com/c/exp/+/634600 LUCI-TryBot-Result: Go LUCI <[email protected]> Auto-Submit: Alan Donovan <[email protected]> Reviewed-by: Jonathan Amsterdam <[email protected]>
Based on the discussion above, this proposal seems like a likely accept. The proposal is to make the unused and experimental functions WriteBundle and ReadBundle in golang.org/x/tools/go/gcexportdata always return an error. |
The gcexportdata package has two functions, WriteBundle and ReadBundle, that have always been marked as experimental and are not used within x/tools, nor, to my knowledge, anywhere else. The only match in GitHub was a single call from apidiff in the
obsoletegolang/exp repo (and forks thereof), which I have since updated.We propose to drop bundle functionality by making both functions return an error unconditionally.
Related:
The text was updated successfully, but these errors were encountered: