Ramanpreet Nara 9f3b6082da Only show deadlock warning when TM eager init is on ... Summary: During setup, TurboModules may synchronously dispatch to the main queue, if they require main queue setup. This is dangerous because it could cause the app to deadlock during TurboModule require. This is why D21654637 (e206e34175) added a warning aginst this. However, this diff had a mistake. We only want to display the warning if TurboModule eager initialization is enabled, because then, we can eagerly initialize the TurboModules before the bridge starts to avoid the problem. D21654637 (e206e34175) instead showed the warning if TurboModule eager init **wasn't** enabled. This isn't useful, because there's no way to avoid the problem with TurboModu eager initialization off. Changelog: [Internal] Reviewed By: sammy-SC Differential Revision: D22529780 fbshipit-source-id: 15238483758b66b1a6addcad948203c64dca96ad		2020-07-14 14:29:59 -07:00
..
core	Only show deadlock warning when TM eager init is on	2020-07-14 14:29:59 -07:00
samples	Rename RCTTurboModuleLookupDelegate to RCTTurboModuleRegistry	2020-07-07 16:25:11 -07:00
.clang-tidy	The life-changing magic of clang-tidying up	2020-02-04 11:09:30 -08:00