Stephen Edwards comments

Results 44 comments of


                                            Stephen Edwards

trafficstars

Method Resolution failing across modules when @Composable fun has a @Composable lambda and called within launchMolecule

I thought so too but could not reproduce in stock Compose.

Move threading concerns to API surface

> Aside from that, I wonder, what's the behavior of this when you are indeed on the main thread: > > ``` > withTimeout(5.seconds) { > withContext(Dispatchers.Main.immediate) { > continue()...

Do not change Workflow API for COmpose

This looks harder to do than originally thought. Not a rabbit hole that makes sense to go down now as we would have to understand more about the "Data Anchor"...

Using `verifyActionResult` and `testNextRender` sequentially results in confusion on external shared states

cc @0legg who may have thoughts on this given he championed `testNextRender`

Compose in the Runtime Take 3

OK so I have updated this with a recent commit that isolates all of teh Compose optimizations as a plugin module

Compose in the Runtime Take 3

1. Trying to call into the Compose runtime directly (without it being a Composable) was a dead end for now as I worked on it for a bit with Zach...

Proof of Concept use compose for workflow logic

> I like the simplicity of this approach, and I think it will be even simpler after fixing the state issues I commented about. > > One other general comment...

Thoughts on decoupling render pass from view updates, and better support support for immediate state change / output

@rjrjr I'm not so sure that the migration effort would be so tedious if we can find a way to map the `WorkflowState` to `WorkflowAction` using just static analysis of...

Thoughts on decoupling render pass from view updates, and better support support for immediate state change / output

@rjrjr I'm starting to parse out the different streams of work/thoughts here: 1. Conflating renderings in the WorkflowRunner with some frame rate before they hit the UI layer. 2. Holding...

Thoughts on decoupling render pass from view updates, and better support support for immediate state change / output

The issue with a naive implementation of (2) - "holding off on render() until action queues are empty" is that we would need to pump all the individual node's actions...