Projection tooling features for Swift interop

[kotlarmilos]

Overview

This issue defines workstreams and tracks the progress of implementing and shipping the projection tooling. Currently, the projection tooling and StoreKit bindings are available as an experimental NuGet packages in dotnet-experimental feed.

Workstream: Swift language features

Based on the selected frameworks, the following Swift language features are in use:

• [Swift language features] Implement Swift enums in C# #2823
• [Swift language features] Implement Swift protocols in C# #2824
• [Swift language features] Implement Swift closures in C# #2828
• [Swift language features] Implement Swift tuples in C# #2933
• [Swift language features] Implement Swift classes/ actors in C# #2934
• [Swift language features] Implement common interfaces in projections (IEnumerable, ICollection, IDisposable) #2829
• [Swift language features] Improve UX of generated bindings #2935
• [Swift language features] Implement Any / Some in C# #2835

Workstream: Swift runtime features

To support the mentioned language features, the following runtime features are required:

• [Swift runtime features] Implement Swift existential containers #2841

Workstream: Projection tooling

To generate bindings, we need projection tooling that includes the following components (based on the current design):

• [Projection tooling] Design projection tooling to be extensible and ensure it outputs only supported types #2843
• [Projection tooling] Refactor projection tooling to be extensible and ensure it outputs only supported types #2845
• [Projection tooling] Projection tooling improvements #2846

Workstream: Shipping

We need the following infrastructure:

• [Swift shipping] Performance benchmarking framework for Swift projection tooling #2586
• [Swift shipping] Improve testing framework #3068

Note

This effort is experimental and not officially supported.