perf(codegen): reorder match arms based on usage patterns #14496
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Reorders Statement and Expression match arms in
oxc_codegento align with parser frequency, improving branch prediction performance.Changes
Statement match reordering:
BlockStatement,ExpressionStatement,VariableDeclaration,IfStatement,ReturnStatement,FunctionDeclarationForStatement,WhileStatement,DoWhileStatement,SwitchStatement, etc.WithStatement,DebuggerStatementExpression match reordering:
Identifier,StaticMemberExpression,ComputedMemberExpression,CallExpressionNumericLiteral,StringLiteral,BooleanLiteral,NullLiteralThe new order follows the parser's pattern matching sequence (from
parse_statement_list_itemandparse_primary_expression), which reflects real-world JavaScript/TypeScript code frequency.Test plan
oxc_codegentests pass (86 passed)oxc_transformerverified (30 tests passed)just fmt🤖 Generated with Claude Code