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
JSStringCreateWithCFString can now use CFIndex #9542
Conversation
EWS run on previous version of this PR (hash 4de6dec) |
CC @JonWBedard |
EWS run on previous version of this PR (hash 3d4bab3)
|
EWS run on previous version of this PR (hash 3719ff3)
|
EWS run on previous version of this PR (hash 96f6630)
|
EWS run on current version of this PR (hash 558c9d7)
|
Do you think we can merge this? @emw-apple |
@Constellation May we please commit this? |
https://bugs.webkit.org/show_bug.cgi?id=251619 <rdar://problem/6806478> Reviewed by Yusuke Suzuki. The original size_t workaround came about 14 years ago, right when Apple was still compiling for PowerPC. Basically, so many devices ran on 32 bits. A long type can hold onto the required length now, so we no longer need to worry about it. *Source/JavaScriptCore/API/JSStringRefCF.cpp: JSStringRef JSStringCreateWithCFString(CFStringRef string): Canonical link: https://commits.webkit.org/260083@main
558c9d7
to
115f237
Compare
Committed 260083@main (115f237): https://commits.webkit.org/260083@main Reviewed commits have been landed. Closing PR #9542 and removing active labels. |
watchOS ARM64_32's CFIndex is 32bit. So we should revert this. |
Reverted in #9941 |
115f237
558c9d7