change: fix build with go 1.20 #1216
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
go4.org/unsafe/assume-no-moving-gc has to be updated to a version that explicitly defines go 1.20 as safe for this program to build with go 1.20
|
Nice, thank you @paper42 ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Fixes build with go 1.20
Closes #1207
Why
go4.org/unsafe/assume-no-moving-gc has to be updated to a version that explicitly defines go 1.20 as safe for this program to build with go 1.20
Implications
no changes, the dependency update only marks go 1.20 as supported which fixes the build with go 1.20
this PR is the result of running these commands in the project root and the docgen directory