Daniel Martí

Just a thought - if you want realistic benchmarks, perhaps ask through more public channels like the Go mailing list or twitter/bluesky, as I imagine only a handful of people...

I made multiple fixes to encoding/json over the years, similar to yours, which were reverted due to backwards compatibility issues. Like @dsnet says, the way forward is v2. Yes, it...

@OJFord you want `go mod why -m`, as `go mod why` works on packages. If `go mod why -m` still tells you that a module is not needed even when...

Still present as of v0.13.0-rc.1.

If someone wants to investigate how to avoid issues with common antivirus software, you're welcome to post your findings here or send patches. I don't have an interest in looking...

I am working on this - later than previous releases, and perhaps not in time for the final Go 1.23 release, but I will finish it.

I _think_ all the changes above should mean complete support. It is very late and I'm going to sleep before CI has had a chance to finish.

Ah, I broke Go 1.22. I know how to fix it, but that will be for tomorrow.

https://github.com/burrowers/garble/pull/871 should be ready now; reviewers welcome. There are a number of commits to split up each of the steps I had to take.

Please try master and let me know how it works with Go 1.23. I will tag a release in a day's time unless any bugs or regressions are reported.