Summary: | Use ASCIILiteral with applicationBundleIsEqualTo in RuntimeApplicationChecksCocoa | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Joseph Pecoraro <joepeck> | ||||
Component: | WebCore Misc. | Assignee: | Joseph Pecoraro <joepeck> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | achristensen, commit-queue, darin, joepeck, webkit-bug-importer, ysuzuki | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Joseph Pecoraro
2018-05-23 21:25:35 PDT
Created attachment 341169 [details]
[PATCH] Proposed Fix
Comment on attachment 341169 [details]
[PATCH] Proposed Fix
r=me
Comment on attachment 341169 [details] [PATCH] Proposed Fix Clearing flags on attachment: 341169 Committed r232148: <https://trac.webkit.org/changeset/232148> All reviewed patches have been landed. Closing bug. Can’t we make the function take a const char* instead? Why make a WTF::String at all? (In reply to Darin Adler from comment #6) > Can’t we make the function take a const char* instead? Why make a > WTF::String at all? I'd be fine with that too. In this case either would work just fine. (In reply to Joseph Pecoraro from comment #7) > (In reply to Darin Adler from comment #6) > > Can’t we make the function take a const char* instead? Why make a > > WTF::String at all? > > I'd be fine with that too. In this case either would work just fine. We should definitely do that. There is no reason to create and destroy a String when these functions are called. On the other hand, the work is only done the first time each is called, so it’s a tiny efficiency. |