show edges for mo.state getters and setters in the dependency graph about marimo

[alefminus]

Importantly the case of a single cell containing getter and setter does work (does not cause an infinite loop, only evaluates once when caused to evaluate), so is there some special handling for it? perhaps it can be elaborated to cover this? or maybe a complete check for loops should be done (i.e. walking the graph) and avoided? Special edges in the dependency graph also could help, showing the Cell_containing_setter_call -> Cell_containing_getter_call connection?

[akshayka]

call getter and setter from same function (found it while trying to implement a log for serial connection date, example shows an example of a counter)

For such cases, pass a function to set_state instead of calling get_state to avoid re-queuing the cell for execution: set_state(lambda v: v + 1).

so is there some special handling for it?

There is some special handling, described in this section:

https://docs.marimo.io/guides/state.html#updating-state

We don't do much any runtime analysis of the graph (it opens up a can of worms that is difficult to reason about). We might be able to add a debugging feature that highlights "state" edges in the dependency viewer.

My preference is to leave as is -- I know it's confusing but I don't see any clean solutions -- and instead encourage people to pass functions to set_state.

[alefminus]

Alright, I thought working on the additional edges in the dependency sidebar would be cool, so if you change your mind about it let me know :) Closing for now.

[akshayka]

Alright, I thought working on the additional edges in the dependency sidebar would be cool, so if you change your mind about it let me know :) Closing for now.

Oh, yes that would be cool! I suppose it could even be done with some careful static analysis.

I was mostly expressing hesitation of detecting cycles at runtime, or further modifying the rules of how state updates are propagated. But if you have ideas I'm open to hearing them