Before with the naive GOPATH workflow and also with vendoring, it was super
easy for me to debug problems with and contribute to upstream packages.
With vgo, I can't just cd into vendor/github.com/foo/bar to test out fixes
for bugs, etc. Without vendoring I could just cd into
$GOPATH/src/gith
ttps://research.swtch.com/vgo-tour for more details.
>
> On Tuesday, February 27, 2018 at 1:47:40 PM UTC-8, Robert Carlsen wrote:
>>
>> Before with the naive GOPATH workflow and also with vendoring, it was
>> super easy for me to debug problems with and contribute to upstr
I also agree that the test caching should be opt-in.
On Friday, December 8, 2017 at 10:28:47 AM UTC-7, Aaron Lefkowitz wrote:
>
> There's two features that are in Go 1.10 that are opt-out new defaults. I
> sincerely apologize for not being active enough to spot them before now.
>
> > The go test
FWIW https://github.com/rwcarlsen/goexif (my neglected of late project) has
some rudimentary and (somewhat) generic tiff parsing capability. I'm not
volunteering for anything - just thought it might be a useful reference for
someone working on this sort of thing.
On Thursday, July 28, 2016 at
