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 wrote: > > Hi, > > I am looking to create a gofix for one of my projects. I thought of > importing the code in > https://github.com/golang/go/tree/master/src/cmd/fix so that I could > simply write a plugin, build a binary and give it to people who import > my code. > > However, I do not see any exported symbols in this code. That leaves > me with only one choice - that I copy the code and then write the > plugin on top of it. That does not sound like a very great idea as > compared to being able to import the package itself. > > Is there any particular reason for not exporting any symbols in the gofix > code? > > Thanks, > Anuj Agrawal > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
