- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 709
 
perf(linter): update linter codegen to support wildcard with empty tuple #14611
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
perf(linter): update linter codegen to support wildcard with empty tuple #14611
Conversation
          
 How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue: 
 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.  | 
    
          
CodSpeed Performance ReportMerging #14611 will not alter performanceComparing  Summary
 Footnotes
  | 
    
          Merge activity
  | 
    
…ple (#14611) Returning `()` in the wildcard of a match block like `match node.kind() { ... }` is effectively the same as `_ => {}`, we just didn't support this syntax yet. +1-2% on the linter benchmarks. <img width="717" height="373" alt="Screenshot 2025-10-14 at 11 51 51 PM" src="https://github.com/user-attachments/assets/5c5b03f0-15b2-4a2f-b7e5-ab57c61634b5" />
41974d1    to
    90f5f89      
    Compare
  
    47b09dd    to
    48e3348      
    Compare
  
    
Returning
()in the wildcard of a match block likematch node.kind() { ... }is effectively the same as_ => {}, we just didn't support this syntax yet.+1-2% on the linter benchmarks.