Requestes to terminate the flutter isolate. As the isolate that is
created is backed by a FlutterBackgroundView/FlutterEngine for the
platform implementations, the event loop will continue to execute
even after user code has completed. Thus they must be explicitly
terminate using kill if you wish to dispose of them after you have
finished. This should cleanup the native components backing the isolates.
Requests the isolate to pause. This uses the underlying isolates pause
implementation to pause the isolate from with the pausing isolate
otherwises uses a SendPort to pass through a pause requres to the target
Requests the isolate to resume. This uses the underlying isolates resume
implementation to as it takes advangtage of functionality that is not
exposed, ie sending 'out of band' messages to an isolate. Regular 'user'
ports will not be serviced when an isolate is paused.
Will return a List of UUIDs representing all running isolates.
NOTE: You cannot kill them individually. This information
is only useful if you want to count the number of isolates
Creates and spawns a flutter isolate that shares the same code
as the current isolate. The spawned isolate will be able to use flutter
plugins. T can be any type that can be normally be passed through to
regular isolate's entry point.