Mystery solved. It turns out it was coming from bytes.NewBuffer which was being invoked in the method I listed. Somehow that was attributed to the import line for bytes rather than the line of invocation.
On Tuesday, December 5, 2017 at 10:51:33 AM UTC-8, Dave Cheney wrote: > > No idea. Which version of Go are you using? -- 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.
