Adam Ernst 80c71e5cae Refine RCTJSCExecutor's APIs for using a thread/context that already exists ... Summary: The `initWithJSContextProvider:` API created a `RCTJSCExecutor` with a thread/context that already exists, but it did not solve the problem of loading an actual application script; the `executeApplicationScript:` API is also asynchronous. Create a new merged API that allows you to pass in a pre-created thread/context pair and immediately receive an `RCTJSCExector` that has already executed a specified application script. This also removes the `underlyingJSContext` API entirely, in favor of passing it back in a byref variable in the new API. This minimizes the surface area for API abuse. Reviewed By: bnham Differential Revision: D3545349 fbshipit-source-id: 1c564f44d2a5379b5e6f75640079a28fd7169f67		2016-07-12 05:28:36 -07:00
..
RCTJSCExecutor.h	Refine RCTJSCExecutor's APIs for using a thread/context that already exists	2016-07-12 05:28:36 -07:00
RCTJSCExecutor.mm	Refine RCTJSCExecutor's APIs for using a thread/context that already exists	2016-07-12 05:28:36 -07:00
RCTJSCWrapper.h	Change API for iOS	2016-07-04 09:28:27 -07:00
RCTJSCWrapper.mm	Refactor RCTPerformanceLogger to avoid having global state	2016-07-07 07:29:57 -07:00