Skip to content
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.

Sign up for GitHub

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

Jump to bottom

proposal: cmd/api: a mechanical approach to compatibility issues #13891

Closed
hirochachacha opened this issue Jan 9, 2016 · 0 comments
Closed

proposal: cmd/api: a mechanical approach to compatibility issues #13891

hirochachacha opened this issue Jan 9, 2016 · 0 comments
Labels
FrozenDueToAge

Comments

@hirochachacha
Copy link
Contributor

This is related to #5778.

I think core tool support API compatibility checking is reasonable.
One of the implementations is extending current tool "go tool api".

Like this:

$ go tool api -version 1 local_file_or_directory

version 0 means "go 1.0," 1 means "go 1.1" ... and so on.

I'm not so sure in detail, but I guess implementation is not so hard work.

Walk third party import paths recursively, and check it compatible or not.
We already know location of api.txt.

Thank you.

hiro
@golang golang locked and limited conversation to collaborators Jan 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hirochachacha @gopherbot