[compiler] add fire imports #31797
Merged
[compiler] add fire imports #31797
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This was referenced Dec 15, 2024
jbrown215
force-pushed
the
pr31797
branch
2 times, most recently
from
8a0fce4 to
7aea49f
Compare
jbrown215
added a commit
that referenced
this pull request
Dec 16, 2024
Config flag for `fire` -- --- [//]: # (BEGIN SAPLING FOOTER) Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/31794). * #31811 * #31798 * #31797 * #31796 * #31795 * __->__ #31794
jbrown215
added a commit
that referenced
this pull request
Dec 16, 2024
Makes `fire` a known export for type-based analysis -- --- [//]: # (BEGIN SAPLING FOOTER) Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/31795). * #31811 * #31798 * #31797 * #31796 * __->__ #31795 * #31794
josephsavona
approved these changes
Dec 16, 2024
josephsavona
approved these changes
Dec 20, 2024
| @@ -30,6 +30,7 @@ function Component(props) { | |||
| ## Code | |||
|
|
|||
| ```javascript | |||
| import { useFire } from "react"; | |||
There was a problem hiding this comment.
hmm i think we might want to export this from the compiler runtime? people shouldn't be calling it directly right?
There was a problem hiding this comment.
Yea, Rick and I are still working that out. Will leave this for now until Rick and I settle on it and will put up a PR to change it assuming we stick with that decision
jbrown215
added a commit
that referenced
this pull request
Dec 20, 2024
This is the diff with the meaningful changes. The approach is: 1. Collect fire callees and remove fire() calls, create a new binding for the useFire result 2. Update LoadLocals for captured callees to point to the useFire result 3. Update function context to reference useFire results 4. Insert useFire calls after getting to the component scope This approach aims to minimize the amount of new bindings we introduce for the function expressions to minimize bookkeeping for dependency arrays. We keep all of the LoadLocals leading up to function calls as they are and insert new instructions to load the originally captured function, call useFire, and store the result in a new promoted temporary. The lvalues that referenced the original callee are changed to point to the new useFire result. This is the minimal diff to implement the expected behavior (up to importing the useFire call, next diff) and further stacked diffs implement error handling. The rules for fire are: 1. If you use fire for a callee in the effect once you must use it for every time you call it in that effect 2. You can only use fire in a useEffect lambda/functions defined inside the useEffect lambda There is still more work to do here, like updating the effect dependency array and handling object methods -- --- [//]: # (BEGIN SAPLING FOOTER) Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/31796). * #31811 * #31798 * #31797 * __->__ #31796
Summary:
Adds import {useFire} from 'react' when fire syntax is used.
This is experimentation and may not become a stable feature in the compiler.
--
This was referenced Dec 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary:
Adds import {useFire} from 'react' when fire syntax is used.
This is experimentation and may not become a stable feature in the compiler.
--
Stack created with Sapling. Best reviewed with ReviewStack.