-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[stdlib] use a primary associated type #61093
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
[stdlib] use a primary associated type #61093
Conversation
@swift-ci please test linux platform |
Blocked on rdar://99908987 |
@swift-ci please test macOS platform |
@swift-ci please test linux platform |
@swift-ci please test |
rdar://99908987 was addressed in #70667, unblocking this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These look way more readable! From what I can tell by visual inspection these will definitely work from a source compatibility standpoint and if I follow correctly they shouldn't have any ABI change either.
They don't affect ABI because they're always-emit-into-client. Otherwise the change on |
Express the generic parameter of
UnsafeMutableBufferPointer.initialize(fromContentsOf:)
usingsome
notation(primary associated type).
Follow-up to SE-0370 (#41608), where this API was proposed using primary associated type notation.
Addresses rdar://99909349 (#61094)