Compile with -warnings-as-errors in CI (incl. StrictSendability) #281
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
We were not compiling with
-warnings-as-errors
in CI because some of the reference source code contained deprecation annotations. This meant that we are not getting CI failures for other warnings that we'd like to be clean of; specifically strict concurrency. However, in addition to the file-based reference tests, we now have in-memory snippet-based reference tests, which contain tests for deprecated OpenAPI schemas and operations.Modifications
-warnings-as-errors
locally with environment variable.Result
SWIFT_OPENAPI_STRICT_CONCURRENCY
will enable the same behaviour.Test Plan