Skip to content

perf(lexer): use get_unchecked for byte access in comment parsing#10635

Merged
graphite-app[bot] merged 1 commit intomainfrom
c/04-27-perf_lexer_use_get_unchecked_for_byte_access
Apr 27, 2025
Merged

perf(lexer): use get_unchecked for byte access in comment parsing#10635
graphite-app[bot] merged 1 commit intomainfrom
c/04-27-perf_lexer_use_get_unchecked_for_byte_access

Conversation

@camc314
Copy link
Contributor

@camc314 camc314 commented Apr 27, 2025

our benchmarks for lexer only has a handful of @preserve comments so i doubt perf change will be noticable.

@github-actions github-actions bot added A-parser Area - Parser C-performance Category - Solution not expected to change functional behavior, only performance labels Apr 27, 2025
Copy link
Contributor Author

camc314 commented Apr 27, 2025


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@camc314 camc314 marked this pull request as ready for review April 27, 2025 09:40
@codspeed-hq
Copy link

codspeed-hq bot commented Apr 27, 2025

CodSpeed Instrumentation Performance Report

Merging #10635 will not alter performance

Comparing c/04-27-perf_lexer_use_get_unchecked_for_byte_access (e6d5a44) with main (b31ab87)

Summary

✅ 36 untouched benchmarks

@Boshen Boshen changed the title perf(lexer): use get_unchecked for byte access perf(lexer): use get_unchecked for byte access in comment parsing Apr 27, 2025
@Boshen Boshen added the 0-merge Merge with Graphite Merge Queue label Apr 27, 2025
Copy link
Member

Boshen commented Apr 27, 2025

Merge activity

…10635)

our benchmarks for lexer only has a handful of `@preserve` comments so i doubt perf change will be noticable.
@graphite-app graphite-app bot force-pushed the c/04-27-perf_lexer_use_get_unchecked_for_byte_access branch from 2b27ed3 to e6d5a44 Compare April 27, 2025 10:55
@graphite-app graphite-app bot merged commit e6d5a44 into main Apr 27, 2025
26 checks passed
@graphite-app graphite-app bot removed the 0-merge Merge with Graphite Merge Queue label Apr 27, 2025
@graphite-app graphite-app bot deleted the c/04-27-perf_lexer_use_get_unchecked_for_byte_access branch April 27, 2025 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-parser Area - Parser C-performance Category - Solution not expected to change functional behavior, only performance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants