🍒[cxx-interop] Import custom NS_OPTIONS
correctly
#68046
Merged
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.
Explanation: This makes sure that custom types defined via
NS_OPTIONS
/CF_OPTIONS
macro get imported as enums into Swift. Previously a heuristic based on the type names was used, which didn't work for all possible type names.Scope: There are multiple reports of this issue blocking adoption of C++ interop.
Risk: Low, this changes the code path that is only taken when C++ interop is enabled: without C++ interop enabled,
CF_OPTIONS
expands into a different AST subtree.Original PR: #67865
rdar://112225263