-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[stdlib] use @_transparent in an appropriate spot #59327
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 @_transparent in an appropriate spot #59327
Conversation
@swift-ci please test |
@swift-ci please benchmark |
Performance (x86_64): -O
Code size: -OPerformance (x86_64): -Osize
Code size: -OsizePerformance (x86_64): -Onone
Code size: -swiftlibsHow to read the dataThe tables contain differences in performance which are larger than 8% and differences in code size which are larger than 1%.If you see any unexpected regressions, you should consider fixing the Noise: Sometimes the performance results (not code size!) contain false Hardware Overview
|
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.
Looks reasonable to me! Another thing we can try is to switch to using @inlinable @inline(__always)
in all of these overloads.
FYI #36309 I don't remember the details any more, but it's potentially worth looking at map and flatMap as well. |
This change lgtm! |
This function was inconsistently @inlinable, as opposed to its peers which are @_transparent. As a consequence, the detailed diagnostics surrounding Optional with
==
and!=
differ strangely based on minute details.Resolves rdar://46444561