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): reuse same UID for _this in arrow function transform #5840 👈
• feat(traverse): generate_uid_name method #5839 : 1 other dependent PR (#5841 )
• refactor(transformer): remove repeat code in arrow function transform #5837
• refactor(transformer): deref SymbolId immediately #5836
• perf(transformer): make branch more predictable in arrow function transform #5833
• refactor(transformer): reorder methods in arrow function transform #5830
• fix(transformer): fix stacks in arrow function transform #5828
• refactor(transformer): rename vars in arrow function transform #5827
• refactor(transformer): shorten code in arrow functions transform #5826
• fix(transformer): remove AstBuilder::copy from arrow functions transform #5825
• 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 #5840 will not alter performance

_{Comparing 09-17-perf_transformer_reuse_same_uid_for__this_in_arrow_function_transform (9778a05) with 09-17-feat_traverse_generate_uid_name_method (82e8778)}

Summary

✅ 29 untouched benchmarks

Interesting. generate_uid is now cheap enough that this doesn't make any noticeable difference on benchmarks. Or maybe our benchmarks don't include enough arrow functions containing this for the code to be exercised.