WebCore::ThreadGlobalData should not initialize fields eagerly
Created attachment 423660 [details] Patch
<rdar://problem/75591436>
Comment on attachment 423660 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=423660&action=review > Source/WebCore/platform/ThreadGlobalData.cpp:118 > +void ThreadGlobalData::initializeCachedResourceRequestInitiators() Why the separate initialize*() functions? Seems we could inline all those.
Comment on attachment 423660 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=423660&action=review >> Source/WebCore/platform/ThreadGlobalData.cpp:118 >> +void ThreadGlobalData::initializeCachedResourceRequestInitiators() > > Why the separate initialize*() functions? Seems we could inline all those. Because this should be executed rarely, I've extracted it from inlined part of the function.
Comment on attachment 423660 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=423660&action=review >>> Source/WebCore/platform/ThreadGlobalData.cpp:118 >>> +void ThreadGlobalData::initializeCachedResourceRequestInitiators() >> >> Why the separate initialize*() functions? Seems we could inline all those. > > Because this should be executed rarely, I've extracted it from inlined part of the function. This also allows us not to include CachedResourceRequestInitiators.h EventNames.h QualifiedNameCache.h etc. in the header side.
Comment on attachment 423660 [details] Patch OK
Committed r274705: <https://commits.webkit.org/r274705> All reviewed patches have been landed. Closing bug and clearing flags on attachment 423660 [details].