[2/y] Fix warnings in throwing initializers #284
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
This was referenced Jan 27, 2022
ryanmeisters
approved these changes
Jan 28, 2022
Base automatically changed from
dev/andrewchang-bird/support-swift-5.5
to
master
January 28, 2022 21:06
Allows us to enable Swift warnings-as-errors on the Mockingbird tests target without false positives.
andrewchang-bird
force-pushed
the
dev/andrewchang-bird/fix-initializer-warnings
branch
from
bec1ac2
to
b558190
Compare
andrewchang-bird
deleted the
dev/andrewchang-bird/fix-initializer-warnings
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.
Stack
📚 #287 [5/y] Improve static mocking APIs
📚 #286 [4/y] Enable mocking sources in test bundles
📚 #285 [3/y] Fix read-only subscripts
📚 #284 ← [2/y] Fix warnings in throwing initializers
📚 #283 [1/y] Add backwards compatibility with Swift 5.5
Overview
Fixes compile-time warnings in mocked initializer declarations like the one below:
No calls to throwing functions occur within 'try' expressionTest Plan
Enabled “treat warnings as errors” on the tests target so that the CI can catch regressions in generator warnings.