-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync with go1.23 #19
Sync with go1.23 #19
Conversation
I compared the carry patch commit against the "patch:..." commits in the repo history and it all looks right to me. The other changes look good too. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jpbetz, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
oof... sorry... this was still WIP ... it appears the stdlib json byte use may have regressed between 1.19 and 1.23 and I was chasing that down... will follow that up and resolve or revert before bumping in k/k |
|
yeah, 50% regression in byte use in typed unmarshals from stdlib 1.20 → 1.21 |
My bad. Happy to review follow up when it is ready. |
full change from 1.20 to 1.21: git log --format=oneline upstream/release-branch.go1.20..upstream/release-branch.go1.21 -- src/encoding/json/
|
opened a revert of this at #20 while I dig into the regression |
Revert "Merge pull request #19 from liggitt/go123"
bisected to golang/go@ac27b4d encoding/json: rely on reflect.Value.Grow |
captured test results at https://gist.github.com/liggitt/bf28159afdaabf52b78ac43d86bc6362, will open upstream go issue |
First commit is a straight copy of the json/encoding files from stdlib on the go 1.23 release branch
Second commit is a reapply of carry patches to those files
Third commit is a tweak to make the external dependency check work with go 1.23
go mod graph
behavior