-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[6.2][Concurrency] Hashable funcs should be inlinable for AsyncStream #81127
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
base: release/6.2
Are you sure you want to change the base?
[6.2][Concurrency] Hashable funcs should be inlinable for AsyncStream #81127
Conversation
5442de0
to
5a1e66f
Compare
@swift-ci please test |
@swift-ci please test |
5a1e66f
to
1cfef25
Compare
@swift-ci please test |
@inlinable | ||
@available(SwiftStdlib 6.2, *) | ||
@inlinable |
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.
nit: looks like there are double annotations for some reason – is that intentional?
@@ -55,6 +55,7 @@ func _unlock(_ ptr: UnsafeRawPointer) | |||
@available(SwiftStdlib 5.1, *) | |||
extension AsyncStream { | |||
@safe | |||
@usableFromInline |
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.
tangential question regarding this change – i've for some time wondered if the internal storage for these types could in some way be unified into something like _Storage<Element, E: Error>
since they have so much duplication. does this change make that idea less feasible?
Small review followup for #81064
The impls should be @inlinable.
Original PR: #81126
Radar: rdar://149914179