This repository has been archived by the owner on Sep 10, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Internally, we've been using a special version of
React.createElement
that checks if a functional component is "referentially transparent" and returns its output, rather than creating a React element. Let's call thiscreateEagerElement
and expose it as a public API.We were also using a function called
internalCreateElement
that acts like a curried form of (what is now called)createEagerElement
. This has a slight optimization, which is to avoid checking for referential transparency each time its used. I couldn't think of a good name at the time, but it's actually just a factory in React parlance. We'll call thiscreateEagerFactory
.