Apologies.On Mar 9, 2024, at 1:16 PM, Ian Lance Taylor wrote:This thread has gotten heated. I think it's time to move on to different topics and give this discussion a rest. Thanks.Ian
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsub
When using `binary.Write` for encoding a slice of structs, I encountered
some weird behaviour where memory allocations in a particular path was more
than I expected.
I wrote some benchmarks in the standard library's encoding/binary package
to demonstrate this.
func BenchmarkWriteSlice1000Str
Disregard. Figured out the tool (a little better). Would still love to chat
with some that has in depth experience with it though.
On Fri, Mar 8, 2024, 1:36 PM Colton Freeman
wrote:
> good day all,
> i am not a developer and have just recently stumbled upon the
> `govulncheck` tool from golang.
