Skip to content

Conversation

@mhrawdon
Copy link
Contributor

The original code was correct and these changes overlooked some context as to why the original code was the way it was (e.g., the warnings are due to a compiler bug, #require will already emit an issue).

This reverts commit a6a6bb7.

@mhrawdon
Copy link
Contributor Author

@swift-ci test

…ehavior in PIFLoadingTests"

The original code was correct and these changes overlooked some context as to why the original code was the way it was (e.g., the warnings are due to a compiler bug, #require will already emit an issue).

But we can work around most of the warnings by casting to an optional, which is low-profile and allows us to retain the same approach to these checks, so that has been added where possible.

This reverts commit a6a6bb7.
@mhrawdon mhrawdon force-pushed the mhrawdon/revert-PIFLoadingTests-changes branch from 79a9fd0 to d4eb98c Compare February 10, 2025 19:05
@mhrawdon
Copy link
Contributor Author

@swift-ci test

@mhrawdon mhrawdon merged commit 3922a7d into main Feb 10, 2025
1 of 2 checks passed
@mhrawdon mhrawdon deleted the mhrawdon/revert-PIFLoadingTests-changes branch February 10, 2025 22:17
@grynspan
Copy link

I can offer a workaround, it's just unsightly :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants