On Sun, Mar 18, 2018 at 10:17 PM, wrote:
> Hi Anuj,
>
> Two quick comments.
>
> 1. FYI, in case you didn't see this in the recent vgo dependency
> management discussion, go fix might start to be used much more broadly in
> the not-too-distant future across the go community as a way to help
>
A minor side comment:
On Sunday, March 18, 2018 at 12:47:11 PM UTC-4, thepud...@gmail.com wrote:
>
>
> from golang/tools eg help via
> https://github.com/golang/tools/blob/release-branch.go1.10/refactor/eg/eg.go#L20
>
> Only refactorings that replace one expression with another, regardless
> of
Hi Anuj,
Two quick comments.
1. FYI, in case you didn't see this in the recent vgo dependency
management discussion, go fix might start to be used much more broadly in
the not-too-distant future across the go community as a way to help
automate in some cases the ability to update client code
Anuj Agrawal,
Exporting an API carries a commitment to maintain and support that API. go
fix was a special-purpose command, that was useful before the Go1
compatibility guarantee. I can see no reason to export a go fix API.
Peter
On Thursday, March 15, 2018 at 6:20:47 AM UTC-4, Anuj Agrawal
