News for hackers. Stuff that matters.
Re:Crank.js – Write JSX-driven components with functions, pr... by Kkoala on Saturday April 18, 2020 @07:52AM (#22907070)
> the class is newly instantiated each time a render is going on

No, it's not? Where do you think the state goes, if the instance doesn't hold it?

Re:Crank.js – Write JSX-driven components with functions, pr... by TomMarius on Saturday April 18, 2020 @08:32AM (#22907273)
It's stored internally in React. The instance of your component does not hold the state, just a reference to the state object which is repopulated each render (just like useState, it's the exact same mechanism), and after the render is done, the instance is destroyed.

More here: https://reactjs.org/blog/2015/12/18/react-components-element...

Re:Crank.js – Write JSX-driven components with functions, pr... by zwily on Saturday April 18, 2020 @09:10AM (#22907460)
The instance of the class isn’t destroyed every render... you can keep other state on it too that is persisted between renders, changing it just won’t trigger a render.
Re:Crank.js – Write JSX-driven components with functions, pr... by TomMarius on Saturday April 18, 2020 @10:01AM (#22907774)
You are right. I tried it here, for others: https://codesandbox.io/s/crazy-bush-cg2i0?file=/src/App.js
Re:Crank.js – Write JSX-driven components with functions, pr... by nightski on Saturday April 18, 2020 @10:14AM (#22907875)
Sure that is the way it works now. Is that a guarantee of React though or implicit behavior that could change in the future?
Re:Crank.js – Write JSX-driven components with functions, pr... by boubiyeah on Saturday April 18, 2020 @11:05AM (#22908217)
It's just an implementation detail.
Re:Crank.js – Write JSX-driven components with functions, pr... by exdsq on Saturday April 18, 2020 @03:46PM (#22910526)
I don’t know how this library or React work, but you could pass the state as an argument to itself - then what GP said makes sense.