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] Fixture to show current behavior of nested function declarations #30921

Closed
wants to merge 1 commit into from

Conversation

mvitousek
Copy link
Contributor

@mvitousek mvitousek commented Sep 9, 2024

…ations

Summary:
Shows both memoized and unmemoized function declarations

[ghstack-poisoned]
Copy link

vercel bot commented Sep 9, 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 Sep 9, 2024 1:04am

Copy link
Contributor

@josephsavona josephsavona left a comment

Choose a reason for hiding this comment

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

Ok...the example isn't nested though? I don't quite follow what this fixture is trying to test

Comment on lines +11 to +13
function h(x) {
return 2;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

are we intentionally not using x? maybe add a comment with why not

@mvitousek
Copy link
Contributor Author

The idea here was to document the changes in the way we emit function declarations after the next diff... which in retrospect, I muddled by modifying the example in that diff to include additional function calls :|

@mvitousek
Copy link
Contributor Author

Actually not really a useful test case at all, looking more at it

@mvitousek mvitousek closed this Sep 9, 2024
@facebook facebook deleted a comment Sep 11, 2024
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.

3 participants