Skip to content

perf: iterate children using a for loop #694

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

Merged
merged 1 commit into from
Mar 29, 2025

Conversation

43081j
Copy link
Contributor

@43081j 43081j commented Mar 29, 2025

Spread is slower here than iterating through the converted children and pushing them individually.

Additionally, spreading the args can result in a large number of params which can cause other problems (sometimes push will throw).

I suspect the for loop is faster because ...convertChildren(...) has to iterate the full set in order to allocate it to an array in memory, which it then has to iterate to spread as params. Whereas iterating through one at a time means we can add the child to the block without waiting for the entire iterable to finish.

i could be wrong, though. either way this fixes the rare edge case where you can try spread too many args to push

Spread is considerably slower here than iterating through the converted
children and pushing them individually.

Additionally, spreading the args can result in a large number of params
which can cause other problems (sometimes `push` will throw).

I suspect the for loop is faster because `...convertChildren(...)` has
to iterate the full set in order to allocate it to an array in memory,
which it then has to iterate to spread as params. Whereas iterating
through one at a time means we can add the child to the block without
waiting for the entire iterable to finish.
Copy link

changeset-bot bot commented Mar 29, 2025

⚠️ No Changeset found

Latest commit: 4c0d35b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

Try the Instant Preview in Online Playground

ESLint Online Playground

Install the Instant Preview to Your Local

npm i https://pkg.pr.new/svelte-eslint-parser@694

Published Instant Preview Packages:

View Commit

@coveralls
Copy link

Pull Request Test Coverage Report for Build 14146946524

Details

  • 22 of 22 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.002%) to 94.661%

Totals Coverage Status
Change from base Build 14097215751: 0.002%
Covered Lines: 10478
Relevant Lines: 10945

💛 - Coveralls

Copy link
Member

@baseballyama baseballyama left a comment

Choose a reason for hiding this comment

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

Not sure about the performance, but at least this PR will solve the stack overflow issue. So let’s merge it.
Thank you!

@baseballyama baseballyama merged commit 00549ff into sveltejs:main Mar 29, 2025
12 checks passed
@43081j 43081j deleted the perf-spread branch March 29, 2025 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants