-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Critical String fixes and high-value enhancements #9784
Conversation
@swift-ci Please test |
@swift-ci Please test source compatibility |
@swift-ci Please benchmark |
This speeds up construction of a String from large Character representations, and various other operations that would otherwise require additional grapheme breaking just to interpret the Character.
Lock-free programming is almost always a bug. Fixes <rdar://25398370> Data Race in StringBuffer.append (found by TSan)
@swift-ci Please test |
1 similar comment
@swift-ci Please test |
@swift-ci Please benchmark |
@swift-ci Please test source compatibility |
Build comment file:Build failed before running benchmark. |
@airspeedswift @dabrahams Benchmarking results are available if you go to the details of the job. The job failed because it expects to get results back for |
AFAICT when I got to the details I don't get anything I can compare to. I see one set of results for O and O_none. I'm not even sure these are the results for the branch under test, as AFAIK Mishal has the baseline tests run first. |
Given my current understanding of the problem, I'd say the risk here is quite low, FWIW. I'll keep the bug updated, though. |
Explanation: Critical String fixes and high-value enhancements
Scope: security bug fix, source-compatible library extension, optimizations
Radar: rdar://32300763 Critical String fixes and high-value enhancements
Risk: moderate
Testing: Passed full validation + benchmarking on master; passed validation and and source compatibility on the 4.0 branch; benchmark pending.