Remind us again why we wouldn't be able to write a...
# coroutines
d
Remind us again why we wouldn't be able to write a coroutines
Dispatcher
which uses
NSThread
on iOS? I know objects, in native, are 'frozen' when crossing Threads; but as long as we respect that; i.e. treat all data arriving from `Channel`/`Flow` as immutable, would it work? Or is coroutine context (or other internal coroutines machinery) violating this principle itself, such that it really couldn't work yet. IMHO Any iOS/OSX coroutines
Dispatcher
should work with
NSThread
directly, and not Apple's GCD. GCD is itself a 'dispatcher'-like concept so the two layer redundant concept on each other to add complexity with little-to-no value.