🍒 [6.2] [cxx-interop] Import public constructor of C++ foreign reference types as Swift initializers #80715
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: In this change we are enabling Swift to construct C++ foreign reference types directly by calling an initializer, without needing to create wrapper functions in C++ that would construct the object and return it. The Swift compiler would automatically allocate using new operator and call the C++ constructor of the type via a compiler synthesized static factory.
Issue: rdar://131557219
Risk: Low. This doesn't impact existing code but provides a new functionality. The risk of this patch is that the automatic initializers are synthesized for all foreign references types regardless of whether they are used or not. We take enough precaution before we start the synthesis of any AST node to ensure that the synthesized code will compile correctly.
Testing: Added tests to test suite and manually tested by using this on some adopter projects
Original PRs: #79986, #80449, #80659
Reviewer: @Xazax-hun @j-hui