You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 12, 2024. It is now read-only.
I've added the notion of type aliases into the the type database.
You can associate with a module a list of type aliases defined on types in the module. The only example of that (so far) is Foundation.NSRect which maps onto CoreGraphics.CGRect.
What needs to be done is:
go through the public Swift API and find all the type aliases
add them to the type database (right now, swiftCore.xml)
Optional:
Consider if we want more type database files than swiftCore.xml.
Organizing the type databases is less of an issue since every entry in type databases has a module name so they'll end up in the right place no matter what, but it might be nice to do the right thing and organize the elements where they belong.
The text was updated successfully, but these errors were encountered:
I've added the notion of type aliases into the the type database.
You can associate with a module a list of type aliases defined on types in the module. The only example of that (so far) is
Foundation.NSRect
which maps ontoCoreGraphics.CGRect
.What needs to be done is:
go through the public Swift API and find all the type aliases
add them to the type database (right now, swiftCore.xml)
Optional:
Consider if we want more type database files than swiftCore.xml.
Organizing the type databases is less of an issue since every entry in type databases has a module name so they'll end up in the right place no matter what, but it might be nice to do the right thing and organize the elements where they belong.
The text was updated successfully, but these errors were encountered: