Add job to evaluate Go 1.22 loop behavior changes #180
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
Use Go 1.21 series "mirror" image to perform builds using the `loopvar` compiler flag. This new workflow job will be ued to identify loops that compile differently using the new loop semantics introduced as a preview in Go 1.21 and enabled by default with the release of Go 1.22. This new workflow job is set to `continue-on-error` in order to verify that it works as intended. Once it has been proven to work as intended `continue-on-error` will be set to `false` and any identified loop behavior changes will be considered a real CI failure requiring resolution. refs GH-145
atc0005
deleted the
i145-add-job-to-evaluate-for-loop-behavior-changes
branch
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.
Use Go 1.21 series "mirror" image to perform builds using the
loopvarcompiler flag. This new workflow job will be ued to identify loops that compile differently using the new loop semantics introduced as a preview in Go 1.21 and enabled by default with the release of Go 1.22.This new workflow job is set to
continue-on-errorin order to verify that it works as intended. Once it has been proven to work as intendedcontinue-on-errorwill be set tofalseand any identified loop behavior changes will be considered a real CI failure requiring resolution.refs GH-145