-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Projection tooling for Swift interop in .NET 10 #95633
Comments
Tagging subscribers to this area: @dotnet/area-meta Issue DetailsDescriptionThis issue tracks the work for adapting the existing Binding Tools for Swift and shipping it as a product in .NET 9. The projection tooling consists of three main areas: Importing Swift into .NET, Exporting .NET to Swift, and distribution. Below is a list of tasks that needs to be implemented. Please note that the breakdown of the issues does not impose hard deadlines. If some of the functionality does not get upstreamed for a particular preview version, this issue will be updated accordingly. Tasks.NET9 Preview 1
.NET9 Preview 2
.NET9 Preview 3TBD
|
Might want to include "Update BTfS to run on .NET 7 and later" - I'm in the middle of that right now. |
Overview
This issue tracks the progress of implementing and shipping the projection tooling for .NET 10. The primary goal is to release the projection tooling as an experimental NuGet CLI capable of generating bindings for a specific set of Swift APIs, as defined in the use cases. It should follow general principles outlined in the Swift interop proposal.
Currently, the projection tooling is available as an experimental NuGet CLI in dotnet-experimental feed.
Tasks:
Any
/Some
/Never
Note
The projection tooling will be experimental in .NET 10.
The text was updated successfully, but these errors were encountered: