-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[stdlib] fix an indexing inconsistency #38091
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
Conversation
@swift-ci please smoke test |
633e036
to
6fbd01f
Compare
This iteration ranged from `buffer.startIndex` to `buffer.count`, rather than to `buffer.endIndex`. Using `buffer.indices` is a better solution in any case.
6fbd01f
to
17c19fb
Compare
@swift-ci please benchmark |
@swift-ci please smoke test |
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
|
@swift-ci please test windows platform |
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.
What a weird way to spell a range 👍
This iteration ranged from
buffer.startIndex
untilbuffer.count
, rather thanbuffer.endIndex
.The latter is more coherent with the indexing model, even though the former happens to work.
No SR.