Enable warnings as errors in CI #842
Merged
Conversation
This file contains hidden or 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
Motivation: Now that strict concurrency has been adopted the AHC should avoid regressing by treating all warnings as errors in CI and by enabling explicit sendable checking. Modifications: - Add the correct flags to enable explicit sendable checking - Treat warnings as errors in CI Result: Stricter CI
glbrntt added 🔨 semver/patch glbrntt changed the title 
rnro approved these changes May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
Motivation:
Now that strict concurrency has been adopted the AHC should avoid regressing by treating all warnings as errors in CI.
Modifications:
Result:
Stricter CI