Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[compiler][ez] Clean up duplicate code in propagateScopeDeps #31581

Merged
merged 1 commit into from
Dec 16, 2024
Merged

Conversation

mofeiZ
Copy link
Contributor

@mofeiZ mofeiZ commented Nov 19, 2024

Clean up duplicate checks for when to skip processing values as dependencies / hoistable temporaries.

Stack created with Sapling. Best reviewed with ReviewStack.

Copy link

vercel bot commented Nov 19, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
react-compiler-playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 16, 2024 7:10pm

Clean up duplicate checks for when to skip processing values as dependencies / hoistable temporaries.
return;
}
if (value.kind === 'PropertyLoad') {
context.visitProperty(value.object, value.property, false);
Copy link
Contributor

Choose a reason for hiding this comment

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

Doesn't seem to be a equivalent to the context.isUsedOutsideDeclaringScope(lvalue) check in the new version, is that a semantic change?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ahh that's because we already check context.isUsedOutsideDeclaringScope when building the temporaries sidemap. It's a bit awkward, but we need this information when constructing the temporaries sidemap because:

  • context.isUsedOutsideDeclaringScope represents a reordering barrier
  • the whole point of the temporaries sidemap is to represent reorderable / semantically equivalent expressions
  • it's difficult to defer finding reordering barriers because they may affect multiple temporaries entries i.e. PropertyLoads from non-reorderable values

I originally duplicated this code to decouple temporary sidemap construction from dependency collection. But.. I think that made maintaining this code much more difficult. @mvitousek I'd love feedback on how to make this cleaner!

@mofeiZ mofeiZ merged commit ac17270 into main Dec 16, 2024
19 checks passed
davesnx added a commit to davesnx/react that referenced this pull request Dec 18, 2024
…act into issue-31578-setter-arity-gcc

* 'issue-31578-setter-arity-gcc' of github.com:/davesnx/react:
  [flags] Clean up scheduler flags (facebook#31814)
  Enable debugRenderPhaseSideEffectsForStrictMode in test renderers (facebook#31761)
  Enable disableDefaultPropsExceptForClasses (facebook#31804)
  Turn on useModernStrictMode in test renderers (facebook#31769)
  [compiler][ez] Add shape for global Object.keys (facebook#31583)
  [compiler] Context variables as dependencies (facebook#31582)
  [compiler] Add fire to known React APIs (facebook#31795)
  [compiler] Add option for firing effect functions (facebook#31794)
  [compiler][be] Logger based debug printing in test runner (facebook#31809)
  [compiler][ez] Clean up duplicate code in propagateScopeDeps (facebook#31581)
  [compiler] Repro for aliased captures within inner function expressions (facebook#31770)
  [compiler][be] Playground now compiles entire program (facebook#31774)
  [Flight] Color and badge non-primary environments (facebook#31738)
  [Flight] Emit Deduped Server Components Marker (facebook#31737)
  [Flight] Sort Server Components Track Group ahead of Client Scheduler/Components Tracks (facebook#31736)
  Clean up context access profiling experiment (facebook#31806)
  [Flight] Stack Parallel Components in Separate Tracks (facebook#31735)
  Flag for requestPaint (facebook#31805)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed React Core Team Opened by a member of the React Core Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants