Coder Social home page Coder Social logo

Comments (4)

markerikson avatar markerikson commented on May 21, 2024 1

My general assumption here would be:

  • In the first case, all of the values match the original, so there is never a render queued thanks to the bailout
  • In the second case, one of the values does not match the original, so at that point a render is queued. That can't be canceled or undone, so the last setState(0) doesn't change anything about that.

from react.

markerikson avatar markerikson commented on May 21, 2024 1

I've tried to trace the internals of the early bailout logic a couple times. Tbh it's really complicated, and I don't remember the exact details.

Based on that behavior description, here's my best guess at what happens:

  • First click: normal render queued, parent and child render.
  • Second click: render queued. React renders the parent component, but sees that the queued state change of 3 matches the existing state, and no other components were marked as dirty for this render pass. React bails out of the render pass as soon as the parent is done, without recursing down and no components are committed.
  • Third click: something extra did get saved as part of the second render pass. This time around, React checks that extra value during the setNumber(3) call, sees that the values are the same, and bails out without even scheduling a render.

from react.

eunjios avatar eunjios commented on May 21, 2024

@markerikson

Thank you for your comment. It is helpful to understand. However, I'm still having trouble understanding this specific case:

const [number, setNumber] = useState(0);
const handleClick = () => { 
  setNumber(3);
}

In this code, when the button is clicked for the first time, both the parent and child components are rendered (as expected). Then, on the second click, only the parent component is rendered. And from the third click on, no components are rendered.

This part is very confusing for me in understanding eager bailouts. (I tried to understand it by reading your posts, and it was very helpful, but I'm still having trouble.)

from react.

eunjios avatar eunjios commented on May 21, 2024

@markerikson

Thank you so much for the detailed explanation! It was really difficult to understand the internal logic by tracing the implementation code, but now I understand it.

from react.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.