Devansh Jethmalani

It's definitely doable but to answer your question you'd have to tell me what the runtime behavior is. Basically what happens when the machine in node `a.b.c` takes an event...

Yeah my impression of the spec is similar and I never meant following the spec exactly - what I meant was let's not do something too out of the way...

Great! It doesn't shave that ability, the change I meant was... ```diff - setContext: (updator: (context: Context) => Context) => void + setContext: (context: Context) => void ``` Would you...

> Won't context become stale with this change? It certainly would, though the user can refactor it like this... ```ts effect: function* ({ context }) { let time = context.time;...

Also mention that `T` variants don't follow semver, they'll keep getting strict and might break even without a major bump. Is this good? Because I think this will happen at...

On a gentle note: We might have to discourage or even disallow this kind of usage (meaning the definition not being a literal, here it's a union of two possibilities...

Sure thing. I think once it's available (I think it already is in 4.4?) we'll turn that on for this codebase (because more strict the better). Probably won't break stuff.

Just wanted to give my two cents on types in context of #36, also I only skim read stuff so apologies if I missed something. > what would happen if...

My pleasure! You can continue with the implementation if you want, [as said](https://github.com/cassiozen/useStateMachine/pull/36#issuecomment-863950370) the implementation types need not be fully type safe. I'll start working on the user facing types...

> You are a machine. This is awesome! Hahaha thanks a lot! > Are we also representing the state as a array in case of a flat, single-level state machine?...