Fix accidentally-introduced warnings and regression in test behavior in PIFLoadingTests #135
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
…in PIFLoadingTests Some of the conditional checks had redundant uses of #require, and regressed previous behavior by failing to include an else case to induce a test failure when the condition was not satisfied.
jakepetroules
requested review from
mhrawdon,
mirza-garibovic,
neonichu and
owenv
as code owners
Collaborator
Author
|
@swift-ci test |
|
There is no need for an else case though. An issue is recorded by |
|
(And the warnings were compiler bugs. You missed the discussion I think?) |
Contributor
|
Right, as @grynspan says, these changes aren't necessary:
We should undo these changes as the old version was more compact and ergonomic. I'll put up a PR. |
Contributor
|
Reverting in #138 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Some of the conditional checks had redundant uses of #require, and regressed previous behavior by failing to include an else case to induce a test failure when the condition was not satisfied.