Skip to content

Rename ReactFiberScheduler -> ReactFiberWorkLoop and extract throwException from Unwind#15725

Merged
acdlite merged 2 commits intofacebook:masterfrom
sebmarkbage:renames
May 23, 2019
Merged

Rename ReactFiberScheduler -> ReactFiberWorkLoop and extract throwException from Unwind#15725
acdlite merged 2 commits intofacebook:masterfrom
sebmarkbage:renames

Conversation

@sebmarkbage
Copy link
Copy Markdown
Contributor

This has been bothering me for a while.

The scheduling part is mostly extracted out to the scheduler package.

What's remaining is mostly around the loop around each section of work.
I name it something with Work in it because it's very related to the
BeginWork, CompleteWork and UnwindWork sections.
Our throwing works more like algebraic effects in that it's a separate
phase where we find a handler and we later unwind.
@sebmarkbage sebmarkbage requested a review from acdlite May 23, 2019 21:03
} while (workInProgress !== null);
}

export {throwException, createRootErrorUpdate, createClassErrorUpdate};
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason for putting the exports at the bottom? We're really inconsistent about this. Maybe we should pick one and stick with it.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just copy pasta so at least it's consistent with what it was.

I think the primary reason exports at the bottom are left over from the CommonJS form.

@sizebot
Copy link
Copy Markdown

sizebot commented May 23, 2019

No significant bundle size changes to report.

Generated by 🚫 dangerJS

@acdlite acdlite merged commit 8af1f87 into facebook:master May 23, 2019
@ronald11126
Copy link
Copy Markdown

ronald11126 commented May 23, 2019 via email

NMinhNguyen referenced this pull request in enzymejs/react-shallow-renderer Jan 29, 2020
…eption from Unwind (#15725)

* Rename ReactFiberScheduler to ReactFiberWorkLoop

The scheduling part is mostly extracted out to the scheduler package.

What's remaining is mostly around the loop around each section of work.
I name it something with Work in it because it's very related to the
BeginWork, CompleteWork and UnwindWork sections.

* Extract throwException from UnwindWork

Our throwing works more like algebraic effects in that it's a separate
phase where we find a handler and we later unwind.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants