[compiler] Remove transitive memo check in validatePreserveMemo #30630
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
[ghstack-poisoned]
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This was referenced Aug 7, 2024
facebook-github-bot
added
CLA Signed
React Core Team
mofeiZ
commented
Aug 7, 2024
Comment on lines
+47
to
+53
| if ($[0] !== x) { | ||
| t0 = () => [x, []]; | ||
| $[0] = x; | ||
| $[1] = t0; | ||
| } else { | ||
| t0 = $[1]; | ||
| } |
There was a problem hiding this comment.
Note that this output correctly preserves manual memoization
mofeiZ
commented
Aug 7, 2024
Comment on lines
+76
to
+83
| if ($[1] !== a || $[2] !== t2) { | ||
| t3 = () => [a, x]; | ||
| $[1] = a; | ||
| $[2] = t2; | ||
| $[3] = t3; | ||
| } else { | ||
| t3 = $[3]; | ||
| } |
There was a problem hiding this comment.
This inferred memoization also preserves manual memo
mofeiZ
commented
Aug 7, 2024
| scopes: Set<ScopeId> = new Set(); | ||
| prunedScopes: Set<ScopeId> = new Set(); | ||
| scopeMapping = new Map(); |
There was a problem hiding this comment.
(drive by dead code deletion)
josephsavona
reviewed
Aug 8, 2024
There was a problem hiding this comment.
This seems reasonable. We should probably still fix up ValidateMemoizedEffectDeps and do a transitive check there, but I agree it's fine for ValidatePreserveManualMemo to be only as precise as the original memoization. Especially given the very low percentage of files impacted.
| ``` | ||
|
|
||
| ### Eval output | ||
| (kind: exception) mutate is not defined |
mofeiZ
added a commit
that referenced
this pull request
Aug 8, 2024
ghstack-source-id: 45521370e48a7e83aaeb79cc9a14d3032bdffbe3 Pull Request resolved: #30630
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.
Stack from ghstack (oldest at bottom):
The original version of validatePreserveMemo tried to check that all manual memo declarations are transitively memoized. This may have been intended to stabilize
useEffectby ensuring that optimized components trigger effects minimally.This transitive memoization check only rarely affects compilation output. (Syncing this PR resulted in 12 changes out of tens of thousands of files). This is likely because many
StartMemoizeandFinishMemoizedeps / decls are identifiers with no attached scopes (see #30603 for more complete explanation).Meta internal reviewers: see changes from this PR