09:22 <magopian> hi o/

09:23 <magopian> i'm reading through https://reasonml.github.io/reason-react/docs/en/state-actions-reducer.html#async-state-setting and don't understand why the reducer in "didMount" returns a ReasonReact.NoUpdate while it's obviously doing an update to self.state.timerId

09:23 <magopian> is that an error in the documentation, or am I missing something?

09:31 <magopian> oh, wait, it's mutating the thing, instead of asking for a proper state update. Not sure how i feel about that

09:34 <reynir> Yea that seems odd to me too, although I know nothing about react

09:35 <reynir> Couldn't this result in a mess of copies of the mutable field?

09:36 <reynir> magopian: Maybe you can ask in an issue on the github page?

09:37 <magopian> i believe they use that for "instance variables": https://reasonml.github.io/reason-react/docs/en/instance-variables.html

09:37 <magopian> so it's kind of in-between a state and a props or something along those lines? It's a bit confusing

09:43 <reynir> I'm a bit busy at work, don't really have time to read the documentation - maybe later if you're still around :-)

09:56 <magopian> reynir: it's fine, I believe my question is answered already, but thanks a lot for offering your help!

23:32 <chenglou> @magopian hello!

23:33 <chenglou> that mutation is needed (and a single layer `mutable` field won't do). You're right. The instance vars section is mostly an interop mechanism to regular reactjs patterns