apicompat
apicompat copied to clipboard
bradleyfalzon
apicompat checks recent changes to a Go project for backwards incompatible changes
When I try to run this against a project using Go111Modules I just get an error: ```#!sh $ apicompat import path not found ``` I'm guessing this doesn't support Go111Modules...
This is not a critical issue for me; reporting it for your benefit only. You should prioritize accordingly. I noticed the following unexpected error in GopherCI (https://gci.gopherci.io/analysis/1198) from `apicompat`: ```...
This may have far reaching consequences, or may not at all. There's at least appears to be added `ast.AliasSpec`. See CLs related to https://github.com/golang/go/issues/16339
There's a few cases were we've assumed GOPATH is set in the env, this may no longer be true when go moves to a default go path: https://github.com/golang/go/issues/17262#issuecomment-255880927 Check some...
It's not possible to determine ahead of time which VCS path for a given import path without adding more code. It maybe simpler to not support checking import paths, and...
Currently abicheck is focused on https://golang.org/doc/go1compat - but others might have other philosophies, or may want a strict mode but for it to raise warnings. Ideally, you'd be able to...
Metadata
Owner
Metadata
apicompat checks recent changes to a Go project for backwards incompatible changes