✨ Swift should provide support for internal imports and resilience for all platforms (that can be enabled in SwiftPM) to allow Swift modules to depend on C++ modules without requiring that the clients enable C++ interoperability

[hyp]

Right now, a Swift target that enables C++ interoperability in SwiftPM requires its dependencies to enable C++ interoperability as well.

We can fix it when Swift supports the following:

• internal imports
• resilience for all platforms (that can be enabled in SwiftPM)

This will allow a Swift target to import C++ clang modules using internal qualifier and will allow it to enable resilience. This will ensure that the dependencies that want to use such Swift target do not have to enable C++ interoperability unless they desire to do so.

This issue tracks the support for both features in Swift. Once both features are supported we can start supporting this C++ interoperability use case as well.

[hyp]

We will also need to fix:

swiftlang/swift-package-manager#6564

[cherylEnkidu]

Hi @hyp ,

Can I ask some clarifications for this feature?

For example, my package structure is something like:

A.dependencies: [B]

B.dependencies: [C]

In my experiment, if B enabled Swift - Cpp interopability, then it forces A to enable as well, otherwise the code cannot be complied.

Whereas, C doesn't need to enable Swift - Cpp interopability.

It is the correct understanding for this constraints?