-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[stdlib][DNM] Concretize dropFirst/Last/sufix/prefix from Sequence #19998
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][DNM] Concretize dropFirst/Last/sufix/prefix from Sequence #19998
Conversation
@swift-ci please benchmark |
@swift-ci please test source compatibility |
I expect some source compat breakage, question is how much. |
Also it would be more efficient to keep forwarding versions of |
This comment has been minimized.
This comment has been minimized.
Ignoring the type-erased benchmarks which we could fix, this is clearly a big performance and code-size win. |
The two projects that failed the compat suite are due to a deserialization failure that I believe is unrelated/existing. |
a2b0bc9
to
e574a11
Compare
@swift-ci please benchmark |
This comment has been minimized.
This comment has been minimized.
@swift-ci please benchmark |
!!! Couldn't read commit file !!! |
Jenkins issue? |
@swift-ci please benchmark |
Build comment file:Build failed before running benchmark. |
@swift-ci please benchmark |
This comment has been minimized.
This comment has been minimized.
8f582ad
to
b7b3913
Compare
b7b3913
to
05b45a2
Compare
@swift-ci please benchmark |
Build comment file:Performance: -O
Code size: -O
Performance: -Osize
Code size: -Osize
Performance: -Onone
Code size: Swift libraries
How 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 regressions before you merge the PR. Noise: Sometimes the performance results (not code size!) contain false alarms. Unexpected regressions which are marked with '(?)' are probably noise. If you see regressions which you cannot explain you can try to run the benchmarks again. If regressions still show up, please consult with the performance team (@eeckstein). Hardware Overview
|
Further followup to #19995 removing more customization points. This one is different in that it is source breaking – these currently return
SubSequence
whereas this PR changes them to return specific concrete types.