Ensure compatibility with C++ interoperability in Swift #12
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
PSchmiedmayer
approved these changes
Jan 25, 2024
1 task
|
@PSchmiedmayer Seems like the build actions changed their name(?). Could you adjust the branch protection CI requirements? |
|
I documented the need to verify this in CI within #13. |
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.
Ensure compatibility with C++ interoperability in Swift
♻️ Current situation & Problem
Currently, ResearchKit fails to build when you have a project that enables C++ interoperability in Swift. This PR addresses these issues with some minor code changes.
⚙️ Release Notes
📚 Documentation
--
✅ Testing
Manually verified that SpeziQuestionnaire builds and tests with these changes (with and without C++ interoperability enabled).
Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: