Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[go1.20] Fixing a encoding/gob override #1323

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

Merged
merged 1 commit into from
Jul 16, 2024
Merged

Conversation

grantnelson-wf
Copy link
Collaborator

When I started working on go1.20 I added an override to encoding/gob growSlice to replace it's usage of generics. Once I got the transpile to work other issues popped up that hid a mistake. Those other issues are now taking care of so this issue came back up. I fixed the mistake and skipped some tests checking mallocs. Additionally, I checked TestEndToEnd override since it has an old TODO on it. It appears the issue with the Marr field still exist so I left it alone.

The experimental generics can handle encoding/god without the override to growSlice now. The unit-tests pass in the same amount of time (within some variance). However, until generics is ready to get out of experimental mode, the overrides for generics are left in. Even after release of generics, this doesn't affect any exported code so can be cleaned up later.

CI will still not pass after this change. However, encoding/gob's unit-tests should pass.

This is part of #1270

@flimzy flimzy merged commit 11d605d into gopherjs:go1.20 Jul 16, 2024
4 of 8 checks passed
@grantnelson-wf grantnelson-wf deleted the fixGob branch July 16, 2024 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants