Skip to content

Conversation

rasendubi
Copy link
Collaborator

validSemver is super-slow, so having it on the hot path in evaluateCondition adds a ton of overhead (as in, >50%). Push it down, so it's only called for comparison operators.

validSemver is super-slow, so having it on the hot path in
evaluateCondition adds a ton of overhead (as in, >50%).
Copy link
Contributor

@aarsilv aarsilv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice spot and thinking!

@rasendubi rasendubi merged commit 8bae7f9 into main Nov 29, 2024
8 checks passed
@rasendubi rasendubi deleted the perf-valid-semver branch November 29, 2024 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants