8000 perf(es/parser): Optimize `next_token` by bvanjoi · Pull Request #10654 · swc-project/swc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

perf(es/parser): Optimize next_token #10654

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 2 commits into from
Jun 21, 2025

Conversation

bvanjoi
Copy link
Contributor
@bvanjoi bvanjoi commented Jun 20, 2025

No description provided.

@bvanjoi bvanjoi requested a review from a team as a code owner June 20, 2025 18:54
Copy link
changeset-bot bot commented Jun 20, 2025

🦋 Changeset detected

Latest commit: 6ce2a74

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

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

Copy link
codspeed-hq bot commented Jun 20, 2025

CodSpeed Performance Report

Merging #10654 will degrade performances by 3.02%

Comparing bvanjoi:less-compute-in-next-token (6ce2a74) with main (9262a59)

Summary

❌ 1 regressions
✅ 139 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

Benchmark BASE HEAD Change
es/lexer/cal-com 34.2 ms 35.3 ms -3.02%

@bvanjoi bvanjoi force-pushed the less-compute-in-next-token branch from f8dc159 to 5cb81d7 Compare June 20, 2025 19:23
@bvanjoi bvanjoi requested a review from a team as a code owner June 20, 2025 19:23
@kdy1 kdy1 changed the title less compute in next token perf(es/parser): Optimize next_token Jun 21, 2025
@kdy1 kdy1 merged commit 1be2ca0 into swc-project:main Jun 21, 2025
17 checks passed
@kdy1 kdy1 modified the milestones: v1.12.5, Planned Jun 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0