Your org has enabled the Graphite merge queue for merging into main

Add the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

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

• perf(transformer): speed up searching for position to insert new statements #6189 👈
• perf(transformer): look up SymbolId for require only once #6192
• refactor(transformer): insert import statement or require depending on source type #6191
• refactor(transformer): rename methods #6190
• fix(transformer): fix inserting require with front option #6188
• refactor(transformer): convert ModuleImports into common transform #6186
• refactor(transformer): introduce TopLevelStatements common transform #6185
• refactor(transformer): rename VarDeclarationsStore methods #6184
• refactor(transformer): export var_declarations module from common module #6183
• main

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

Join @overlookmotel and the rest of your teammates on Graphite

CodSpeed Performance Report

Merging #6189 will not alter performance

_{Comparing 09-30-perf_transformer_speed_up_searching_for_position_to_insert_new_statements (f028e3c) with main (a949ecb)}

Summary

✅ 29 untouched benchmarks

Hard to see exactly with the noise in the benchmarks, but looks like this hurts perf, rather than improving it. I'll take another look.

I give up. You'd think this would be better, but it appears it's not.